CVE-2025-24148
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 · uneditedThis issue was addressed with improved handling of executable types. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. A malicious JAR file may bypass Gatekeeper checks.
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 confidenceA vulnerability in macOS Gatekeeper allows malicious JAR files to bypass security checks and execute without proper verification. The issue stems from improper handling of executable types in the Gatekeeper mechanism, which normally enforces code signing and notarization requirements.
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< 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.4CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 your macOS versionRun 'sw_vers -productVersion' in Terminal to get the exact version number (e.g., 14.6, 15.3)Affected if The version is less than 13.7.5, or between 14.0 and 14.7.4, or between 15.0 and 15.3.x
-
Verify Gatekeeper statusRun 'spctl --status' in Terminal to check if Gatekeeper is enabledAffected if Gatekeeper is enabled (the bypass affects its JAR verification when turned on)
-
Check for recently opened JAR filesRun 'xattr -l /path/to/file.jar' to inspect quarantine attributes, or check ~/Library/Logs/Jetty or application logs for recent JAR executionsAffected if JAR files show no quarantine attribute (com.apple.quarantine) or were executed without Gatekeeper prompting
-
Inspect Gatekeeper logs for JAR bypassesRun 'log show --predicate 'eventMessage contains "Gatekeeper"' --last 24h | grep -i jar' to search recent system logsAffected if Logs show JAR files executed without Gatekeeper code signing or notarization checks
You are affected if your macOS version falls within the vulnerable ranges AND Gatekeeper is enabled, as the flaw allows unsigned or unnotarized JAR files to execute without proper verification.
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 · scoped13.7.514.7.515.4
Apply the macOS security updates (Ventura 13.7.5, Sonoma 14.7.5, or Sequoia 15.4) to patch the Gatekeeper bypass. Ensure JAR files are only opened from trusted sources.
macOS Ventura 13.7.5 / macOS Sonoma 14.7.5 / macOS Sequoia 15.4 (depending on your current major version)
- Back up your Mac using Time Machine before performing any system update
- Identify your current macOS version by clicking the Apple menu and selecting About This Mac
- For macOS Ventura (13.x) users: Open System Settings > General > Software Update and install macOS 13.7.5
- For macOS Sonoma (14.x) users: Open System Settings > General > Software Update and install macOS 14.7.5
- For macOS Sequoia (15.x) users: Open System Settings > General > Software Update and install macOS 15.4
- Restart your Mac when prompted to complete the installation
- Verify the update was successful by checking About This Mac shows the expected version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24148 — 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-2025-24148 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