This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2026-43701 →

UBUNTU-CVE-2026-43701

Vulnerability in qtwebkit-opensource-src (UBUNTU-CVE-2026-43701)

Summary

Vulnerability in qtwebkit-opensource-src (UBUNTU-CVE-2026-43701). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.52.6-0ubuntu0.24.04.1 or later.

Original description

The description as published by the source.

The issue was addressed with improved checks. This issue is fixed in Safari 26.5.2, iOS 18.7.10 and iPadOS 18.7.10, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, watchOS 26.6. A malicious website may be able to process restricted web content outside the sandbox.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-43701 has been found in qtwebkit-opensource-src.
Risk of unauthorized operations or information disclosure.
What to do: upgrade qtwebkit-opensource-src to 2.52.6-0ubuntu0.24.04.1 or later.
If unsure, ask your IT team or search "qtwebkit-opensource-src UBUNTU-CVE-2026-43701" on the vendor's site.

UBUNTU-CVE-2026-43701 (qtwebkit-opensource-src)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.52.6-0ubuntu0.24.04.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in qtwebkit-opensource-src.

📍 Affected scope

Check the vendor advisory for the affected versions of qtwebkit-opensource-src.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.52.6-0ubuntu0.24.04.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'qtwebkit-opensource-src' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'qtwebkit-opensource-src' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で qtwebkit-opensource-src を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade qtwebkit-opensource-src to 2.52.6-0ubuntu0.24.04.1
```
ステージング環境で 2.52.6-0ubuntu0.24.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。