# CVE-2026-37554: Denial of service in n/a

> Remote attackers can crash the V2X receiver by sending malformed GeoNetworking packets that trigger unhandled OpenSSL exceptions.

- **Severity:** High 7.5 (`CVSS:3.1/AC:L/AV:N/A:H/C:N/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-877p-g3p3-329r

## What is CVE-2026-37554?

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

### Official description

An issue was discovered in Vanetza V2X v26.02 allowing remote unauthorized attackers to cause a denial of service. The vulnerability exists in the GeoNetworking packet processing pipeline where OpenSSL exceptions from ECC point validation (invalid compressed point, point not on curve) are not properly caught by the Router::indicate() call chain. The openssl_wrapper.cpp check() function (line 19) throws openssl::Exception when OpenSSL operations fail. The parser's catch block in parse_secured() should catch these, but the exception escapes through subsequent processing stages (indicate_common, indicate_extended). This causes std::terminate, crashing the V2X receiver.

Weakness: CWE-248 (Uncaught Exception)

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


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

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

## Is CVE-2026-37554 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-37554 is a high-severity denial of service vulnerability in n/a, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-37554 in the wild and no public exploit code.

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

## Sources

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

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