CVE-2026-11799
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUXSS in Focus for iOS / Klar Webkit navigation. This vulnerability was fixed in Focus for iOS 151.3.1 and Klar for iOS 151.3.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA Universal Cross-Site Scripting (UXSS) vulnerability in Focus for iOS and Klar for iOS browsers affecting WebKit navigation. This type of vulnerability allows an attacker to execute malicious scripts in the context of any website, bypassing the same-origin policy.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 151.3.1< 151.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed browser appsCheck the iOS device for Mozilla Focus or Mozilla Klar applications installed from the App StoreAffected if Either Mozilla Focus or Mozilla Klar is present on the device
-
Check Mozilla Focus versionOpen the App Store app, go to Profile > Purchased, find Mozilla Focus, and view the version number. Alternatively, check within the Focus app settings under About or Help sections if availableAffected if The displayed version number is less than 151.3.1
-
Check Mozilla Klar versionOpen the App Store app, go to Profile > Purchased, find Mozilla Klar, and view the version number. Alternatively, check within the Klar app settings under About or Help sections if availableAffected if The displayed version number is less than 151.3.1
-
Confirm vulnerability applicabilityThis vulnerability exists in the WebKit navigation handling within the browser. If the app is installed and running, the affected code is active regardless of specific configurationAffected if The installed version is below 151.3.1, meaning the browser contains the vulnerable WebKit navigation code
A user is affected if Mozilla Focus for iOS or Mozilla Klar for iOS is installed with a version number lower than 151.3.1, as the UXSS vulnerability in WebKit navigation handling is present in those versions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped151.3.1
Update Focus for iOS and Klar for iOS to version 151.3.1 or later to remediate this vulnerability.
Focus for iOS 151.3.1 / Klar for iOS 151.3.1
- 1. Open the App Store on the iOS device
- 2. Search for "Focus" or "Klar" depending on which app is installed
- 3. Verify the installed version by checking the app store listing or device settings
- 4. If the current version is below 151.3.1, tap the Update button to upgrade to version 151.3.1 or later
- 5. Alternatively, enable automatic app updates in iOS Settings > App Store > Automatic Downloads to ensure future updates are applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11799 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data