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

> Attackers can bypass certificate validation by sending OCSP responses without the nextUpdate field, allowing unvalidated certificates to be accepted.

- **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-93493, GHSA-9rhx-p462-pg2j, UBUNTU-CVE-2026-93493

## What is CVE-2026-93493?

CVE-2026-93493 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 `netty-handler-ssl-ocsp` component. A remote attacker can exploit this vulnerability by providing an Online Certificate Status Protocol (OCSP) response that omits the optional `nextUpdate` field. This omission causes the OCSP validation to be silently skipped, leading to applications proceeding with an unvalidated certificate. This can result in a bypass of security controls where certificate validation is expected.

Weakness: CWE-299 (Improper Check for Certificate Revocation)

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


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

Apply the vendor's patch.

## Is CVE-2026-93493 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93493 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: There is no known exploitation of CVE-2026-93493 in the wild and no public exploit code.

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-93493/ (Markdown: https://insights.sbomify.com/CVE-2026-93493/index.md)
```

## Sources

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

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