CVE-2022-28261: Adobe Acrobat Reader DC Annotation Out-Of-Bounds Read Information Disclosure Vulnerability
Acrobat Reader DC version 22.001.2011x (and earlier), 20.005.3033x (and earlier) and 17.012.3022x (and earlier) are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
Security readout for executives and security teams
Plain-English summary
This vulnerability can let a malicious PDF read memory from Adobe Acrobat Reader and potentially expose information useful for bypassing defenses. It requires a person to open a crafted file, so risk is tied to phishing or document-sharing workflows rather than remote unauthenticated scanning.
Executive priority
Handle as a moderate endpoint patching priority. The issue is not presented as actively exploited, but it can support phishing-driven attacks and defense bypass when users open malicious documents.
Technical view
CVE-2022-28261 is a CWE-125 out-of-bounds read in Acrobat Reader DC file parsing. The CVSS 3.1 score is 5.5, with local attack vector, no privileges required, required user interaction, and high confidentiality impact.
Likely exposure
Exposure is most likely on user workstations running Acrobat Reader DC 22.001.2011x and earlier, 20.005.3033x and earlier, or 17.012.3022x and earlier. Server exposure is not indicated by the provided sources.
Exploitation context
The sources say exploitation requires a victim to open a malicious file. The CVE is not listed as KEV, and the supplied evidence does not show active exploitation in the wild.
Researcher notes
This is an information disclosure flaw that may help bypass ASLR rather than directly execute code. Treat it as meaningful in chained exploitation scenarios. The provided sources do not include proof-of-concept status or detailed fixed-version data.
Mitigation direction
Review Adobe APSB22-16 for the applicable Acrobat Reader update guidance.
Update affected Acrobat Reader installations according to vendor guidance.
Reduce user exposure to untrusted PDF attachments and downloads.
Prioritize document-heavy teams and high-risk email users first.
Validation and detection
Inventory Acrobat Reader versions across managed endpoints.
Identify systems at or below the affected version ranges.
Confirm deployed versions align with Adobe APSB22-16 guidance.
Review email and endpoint controls for untrusted PDF handling.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.