CVE-2026-47924
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 · uneditedAcrobat Reader versions 24.001.30365, 26.001.21651 and earlier are affected by a Use After Free vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to disclose sensitive information. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
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 confidenceAdobe Acrobat Reader contains a Use After Free vulnerability in versions 24.001.30365, 26.001.21651 and earlier where memory can be accessed after being freed, potentially allowing disclosure of sensitive memory contents. Exploitation requires a victim to open a maliciously crafted PDF file.
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>= 15.008.20082, < 26.001.21662>= 15.008.20082, < 26.001.21662>= 24.0.0, < 24.001.30383CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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.
-
Identify installed Adobe productOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat) to display the exact version number. Alternatively, right-click the application icon, select Properties, and check the Details tab for the version.Affected if Adobe Acrobat or Adobe Acrobat Reader is installed on the system
-
Confirm exact version numberRecord the full version string shown (for example: 24.001.30383 or 15.008.20082). Ensure you capture all three numeric segments as shown in the About dialog.Affected if The version number cannot be determined or is not fully visible
-
Compare against affected version rangesCheck if your version falls within any of these ranges: Acrobat Dc or Reader Dc version 15.008.20082 through 26.001.21661 (inclusive), or Acrobat version 24.0.0 through 24.001.30382 (inclusive).Affected if The installed version is equal to or greater than 15.008.20082 AND less than 26.001.21662 for Dc versions, OR equal to or greater than 24.0.0 AND less than 24.001.30383 for standard Acrobat versions
You are affected if Adobe Acrobat or Adobe Acrobat Reader is installed and the version number falls within the affected ranges (15.008.20082 to 26.001.21661 for Dc products, or 24.0.0 to 24.001.30382 for standard Acrobat).
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 · scoped24.001.3038326.001.21662
Update Adobe Acrobat Reader to the latest patched version beyond 26.001.21651 to remediate this vulnerability. Organizations should deploy updates through their patch management systems and remind users not to open untrusted PDF files.
Acrobat 24.001.30383+ or Acrobat/Acrobat Reader DC 26.001.21662+ (depending on product track)
- 1. Identify the installed Adobe Acrobat/Acrobat Reader version via Help > About Adobe Acrobat/Reader
- 2. For Acrobat (2024 track, version 24.x): upgrade to version 24.001.30383 or later
- 3. For Acrobat/Acrobat Reader DC (2020 track, version 26.x): upgrade to version 26.001.21662 or later
- 4. Download the update from the official Adobe website or use the built-in automatic update feature (Help > Check for Updates)
- 5. Restart the application after installation
- 6. Verify the installed version matches or exceeds the fixed version for your product track
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2026-47924 — 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-47924 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