# CVE-2026-100132: Acrobat for Edge | Out-of-bounds Read (CWE-125)


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-c3gc-gvf4-598f

## What is CVE-2026-100132?

CVE-2026-100132 is a medium-severity vulnerability in Adobe Acrobat for Edge, published on 20 Oct 2026. 

### Official description

Acrobat for Edge is affected by an out-of-bounds read 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 visit a maliciously crafted URL or interact with a compromised web page.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-100132?


## How do I fix CVE-2026-100132?

No fix has been published for CVE-2026-100132 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100132 being exploited?

There is no known exploitation of CVE-2026-100132 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100132 and fix it if it is affected.

What it is: CVE-2026-100132 is a medium-severity vulnerability in Adobe Acrobat for Edge, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-100132 in the wild and no public exploit code.

Affected product: Adobe Acrobat for Edge. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100132/ (Markdown: https://insights.sbomify.com/CVE-2026-100132/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100132
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100132
- OSV: https://osv.dev/vulnerability/CVE-2026-100132

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100132/
Summaries are generated and may contain mistakes; the official description above is the record.