# CVE-2026-44905: Vanetza: Remote Denial of Service via Uncaught OER Encoding Exception in Cryptographic Verification

> Remote attackers can crash the Vanetza V2X application by sending crafted packets that trigger an uncaught exception during cryptographic verification.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 26 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-q9fq-3rx9-7xcv

## What is CVE-2026-44905?

CVE-2026-44905 is a high-severity denial of service vulnerability in riebl vanetza, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vanetza is an open-source implementation of the ETSI C-ITS protocol suite. In 26.02 and earlier, a denial-of-service vulnerability was identified in the cryptographic verification pipeline of Vanetza. When processing incoming V2X messages, the ASN.1 decoder accepts the structure as syntactically valid. However, this reveals a logic-based protocol failure where semantic constraints on specific fields are only strictly enforced during OER re-encoding. Specifically, if a crafted packet contains a certificate where the Psid (Provider Service Identifier) sub-type violates subtype constraints (e.g., out-of-range or invalid CHOICE variant), it is accepted during initial parsing, where subtype constraints are not enforced. Later, when StraightVerifyService attempts to calculate a message hash for cryptographic verification, it must re-encode the signing certificate. The underlying ASN.1 wrapper (asn1c_wrapper.cpp) detects the semantic violation during encoding and raises a std::runtime_error. This exception is not caught within the encoding path and propagates to std::terminate, resulting in immediate process termination. This vulnerability is fixed with commit e1a2e2709210d309458c3d77f98d50dec26c0df0.

Weakness: CWE-248 (Uncaught Exception)

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


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

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

## Is CVE-2026-44905 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44905 is a high-severity denial of service vulnerability in riebl vanetza, published on 26 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-44905 exists.

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

## Sources

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

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