# CVE-2026-45615: mouse07410/asn1c: 1-byte Heap Out-of-Bounds Read in `INTEGER_decode_oer` via Malformed OER Payload

> Remote attackers can cause denial of service or logic errors via a heap out-of-bounds read in asn1c-generated code when parsing malformed OER payloads.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-wxx8-76rw-96j2

## What is CVE-2026-45615?

CVE-2026-45615 is a high-severity memory corruption vulnerability in mouse07410 asn1c, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mouse07410/asn1c is an ASN.1 compiler. In 1.4 and earlier, a memory safety vulnerability was identified in the OER decoding skeleton files generated by asn1c (specifically INTEGER_oer.c). When parsing a maliciously crafted, zero-length OER payload for a variable-length, non-negative INTEGER type, the decoder fails to validate the required bytes before extracting the Most Significant Bit (MSB). This forces a precise 1-byte Heap Out-of-Bounds (OOB) Read. Because asn1c generated code is primarily deployed to parse untrusted network inputs (such as V2X network protocols, 5G telecom headers, or X.509 certificates), when the decoder processes untrusted network-originated input, a remote attacker can exploit this to cause a Denial of Service (DoS) or trigger incorrect integer interpretation in downstream applications (e.g., protocol state poisoning or logic bypass).

Weakness: CWE-20 (Improper Input Validation), CWE-130 (Improper Handling of Length Parameter Inconsistency), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-45615 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45615 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45615 is a high-severity memory corruption vulnerability in mouse07410 asn1c, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45615 exists.

Affected product: mouse07410 asn1c. 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-45615/ (Markdown: https://insights.sbomify.com/CVE-2026-45615/index.md)
```

## Sources

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

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