SafariWeb browser · Apple
CVE-2022-32861
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 · uneditedA logic issue was addressed with improved state management. This issue is fixed in Safari 15.6, macOS Monterey 12.5. A user may be tracked through their IP address.
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 · high confidenceSafari in macOS Monterey 12.5 and Safari 15.6 contains a logic error in state management that allows a user's IP address to be exposed or persisted across sessions, enabling unauthorized tracking of users without their explicit consent.
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
SafariWeb browser
< 15.6>= 12.0.0, < 12.5CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check installed Safari versionOpen Safari, then go to Safari > About Safari to view the version numberAffected if Version is lower than 15.6
-
Check macOS versionClick Apple menu > About This Mac to view the macOS versionAffected if macOS is 12.0.0 through 12.4 (Monterey, not yet updated to 12.5)
-
Verify Safari and macOS combinationConfirm both the Safari version and macOS version from the previous two checksAffected if Safari is below 15.6 while running on any macOS Monterey version from 12.0.0 through 12.4
You are affected if Safari version is below 15.6 on a system running macOS Monterey 12.0.0 through 12.4, because the state management flaw that can expose or persist IP addresses 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 · scoped12.515.6
Apply the vendor-supplied patch by updating to Safari 15.6 or macOS Monterey 12.5 or later, which implements proper state isolation to prevent IP address leakage.
Safari 15.6, macOS Monterey 12.5
- Check current Safari version by opening Safari and selecting Safari > About Safari
- Check current macOS version by clicking Apple menu > About This Mac
- If Safari version is less than 15.6, open System Preferences > Software Update and install the Safari 15.6 update
- If macOS version is between 12.0.0 and 12.4.x, open System Preferences > Software Update and install the macOS Monterey 12.5 update
- After updating, verify the fixes are applied by checking Safari > About Safari shows version 15.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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-2022-32861 — 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-2022-32861 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