# CVE-2026-93578: Security feature bypass in Red Hat build of Apache Camel for Spring Boot 4

> Attackers can bypass certificate revocation checks by forging OCSP responses, allowing revoked certificates to be accepted by applications using Netty.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-93578, GHSA-4wrp-2fvc-9x8r, UBUNTU-CVE-2026-93578

## What is CVE-2026-93578?

CVE-2026-93578 is a medium-severity vulnerability in Red Hat build of Apache Camel for Spring Boot 4, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in Netty's Online Certificate Status Protocol (OCSP) Client. The client fails to verify the 'id-kp-OCSPSigning' Extended Key Usage (EKU) in OCSP responder certificates. A remote attacker, holding any valid certificate issued by the same Certificate Authority (CA), can exploit this by forging 'GOOD' OCSP responses for revoked certificates. This bypasses certificate revocation checks, allowing applications using Netty's OCSP Client to accept certificates that should have been revoked, leading to an authorization bypass.

Weakness: CWE-1035

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


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

Upgrade to a fixed version.

## Is CVE-2026-93578 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93578 is a medium-severity vulnerability in Red Hat build of Apache Camel for Spring Boot 4, published on 18 Sep 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-93578 exists.

Affected product: Red Hat build of Apache Camel for Spring Boot 4. 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-93578/ (Markdown: https://insights.sbomify.com/CVE-2026-93578/index.md)
```

## Sources

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

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