CVE Tools

CVE-2018-4962

Exploitation likely. EPSS gives it a 11% chance of exploitation in the next 30 days. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • n/a Adobe Acrobat and Reader 2018.011.20038 and earlier, 2017.011.30079 and earlier, and 2015.006.30417 and earlier versionsAffected: Adobe Acrobat and Reader 2018.011.20038 and earlier, 2017.011.30079 and…Upgrade to: not statedStated by: CVE record
  • Adobe Acrobat DcAffected: ≥ 15.006.30060, ≤ 15.006.30417Upgrade to: after 15.006.30417Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check which Adobe Acrobat DC / Acrobat and Reader version you have installed (Help → About) and compare it to 2018.011.20038, 2017.011.30079, and 2015.006.30417.
  2. If your version is at or below those listed (or older), upgrade using Adobe’s security update for APSB18-09.
  3. If you cannot update right away, stop opening PDF/Office attachments from unexpected emails and use a dedicated viewer workflow for untrusted files (for example, open in a controlled environment or review externally).

What it is

From the CVE record

Adobe Acrobat and Reader versions 2018.011.20038 and earlier, 2017.011.30079 and earlier, and 2015.006.30417 and earlier have an Out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.

In plain language

Written by AI from the record

CVE-2018-4962 is a bug in older Adobe Acrobat/Reader versions that can let an attacker read some memory they shouldn’t; if you don’t actively open untrusted documents, it’s less likely to affect you, but updating is still a good idea.

CVE-2018-4962 is an out-of-bounds read in Adobe Acrobat and Reader that can result in information disclosure when processing a crafted file/document; there’s no confirmed public KEV entry or known public exploit code, but Adobe has issued remediation.

If you're affected

  • Confidential document data disclosure
  • Sensitive information exposure
  • Increased risk from phishing attachments

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS96th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

11% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

23 events over 2998 days, from the signal feeds we watch.

  1. EPSS band change0 → moderateepss band change
  2. EPSS band changemoderate → 0epss band change
  3. EPSS band change0 → moderateepss band change
  4. EPSS band changemoderate → lowepss band change
  5. EPSS band change0 → moderateepss band change
  6. EPSS band changemoderate → 0epss band change

Affected products

And 2 more affected products. See all after sign-in

Technical detail

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Acrobat Reader Dc, not every advisory.