Skip to main content
Mallory
LowVulnerability

CVE-2007-2580: Keychain Password Disclosure in Apple Safari via JavaScript and AppleScript

Published May 9, 2007 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS1.9Low · v2
EPSS0.74%56th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Apple
IdentifiersCVE-2007-2580CWE-200

An unspecified vulnerability in Apple Safari allows local users to access sensitive information, specifically saved keychain passwords, by leveraging the document.loginform.password.value JavaScript parameter when loaded from an AppleScript script. This suggests a flaw in the way Safari exposes form data to scripts, enabling unauthorized access to credentials stored in the macOS keychain.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Local attackers can obtain saved keychain passwords, potentially leading to unauthorized access to user accounts and sensitive data. The exposure of keychain credentials can facilitate further compromise of the affected system and any services for which the credentials are used.

Mitigation

If you can’t patch tonight, do this now.

Restrict local access to the system to trusted users only. Avoid running untrusted AppleScript scripts or JavaScript code that interacts with login forms. Monitor for suspicious local activity that may indicate exploitation attempts.

Remediation

Patch, then assume compromise.

Apply the security updates provided by Apple that address this vulnerability. Ensure Safari and macOS are updated to the latest versions where this issue is resolved.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AppleSafariapplication
FAQ

Frequently asked questions

Is CVE-2007-2580 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2007-2580 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2007-2580?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2007-2580. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2007-2580?
Apply the security updates provided by Apple that address this vulnerability. Ensure Safari and macOS are updated to the latest versions where this issue is resolved.
What products are affected by CVE-2007-2580?
Apple Safari.
How severe is CVE-2007-2580?
CVE-2007-2580 has a CVSS v2 score of 1.9 (Low) and an EPSS score of 0.74% (56th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.