CVE-2021-41795
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 · uneditedThe Safari app extension bundled with 1Password for Mac 7.7.0 through 7.8.x before 7.8.7 is vulnerable to authorization bypass. By targeting a vulnerable component of this extension, a malicious web page could read a subset of 1Password vault items that would normally be fillable by the user on that web page. These items are usernames and passwords for vault items associated with its domain, usernames and passwords without a domain association, credit cards, and contact items. (1Password must be unlocked for these items to be accessible, but no further user interaction is required.)
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 confidenceThe Safari app extension in 1Password for Mac versions 7.7.0 through 7.8.x before 7.8.7 contains an authorization bypass vulnerability. A malicious web page can exploit this to read vault items (domain-associated credentials, credentials without domain, credit cards, and contacts) that would normally be fillable on that page. The attack requires 1Password to be unlocked but requires no additional user interaction.
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>= 7.7.0, < 7.8.7CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm 1Password for Mac is installedOpen Finder, go to /Applications folder, or search for '1Password' in Spotlight to verify 1Password for Mac is present on the systemAffected if 1Password for Mac is not installed on the system
-
Determine the installed 1Password versionOpen 1Password for Mac, click on the 1Password menu in the menu bar, then select 'About 1Password' to view the exact version numberAffected if The installed version is 7.7.0 through 7.8.6 (any version >= 7.7.0 and < 7.8.7)
-
Check if Safari is used as the browserVerify if Safari is the default browser or if Safari is used for browsing. Open Safari, go to Safari > Preferences > General to check the default browser settingAffected if Safari is used as the primary or default browser
-
Verify the 1Password extension is enabled in SafariOpen Safari, go to Safari > Preferences > Extensions, and check if the 1Password extension is enabledAffected if The 1Password Safari extension is enabled
-
Confirm typical unlock state during browsingConsider whether 1Password is typically left unlocked while browsing, or if the vault is frequently in an unlocked state during normal useAffected if 1Password is frequently left unlocked while using the browser
A user is affected if they have 1Password for Mac version 7.7.0 through 7.8.6 installed with the Safari extension enabled and the vault unlocked during web browsing.
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 · scoped7.8.7
Update 1Password for Mac to version 7.8.7 or later to remediate this vulnerability.
1Password for Mac 7.8.7
- Open 1Password for Mac
- Navigate to 1Password > About 1Password to verify the current version
- If the version is 7.7.0 or higher but below 7.8.7, proceed to upgrade
- Download 1Password for Mac version 7.8.7 from the official 1Password website (support.1password.com) or use the built-in update mechanism if available
- Install the 7.8.7 update by following the on-screen prompts
- After installation, verify the version is now 7.8.7
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41795 — 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-2021-41795 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