# CVE-2024-0853: OCSP verification bypass with TLS session reuse

> Attackers can bypass OCSP stapling verification by reusing cached TLS sessions, allowing connections to servers with revoked certificates.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 3 Feb 2024
- **Updated:** 20 Jun 2025
- **Also known as:** ALPINE-CVE-2024-0853, AZL-34061, AZL-34648, BELL-CVE-2024-0853, CLEANSTART-2026-JD03338, CURL-CVE-2024-0853, DEBIAN-CVE-2024-0853, GHSA-697h-9h25-w4fm, JLSEC-2026-412, UBUNTU-CVE-2024-0853, openSUSE-SU-2024:13637-1

## What is CVE-2024-0853?

CVE-2024-0853 is a medium-severity vulnerability in Haxx Curl, published on 3 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

curl inadvertently kept the SSL session ID for connections in its cache even when the verify status (*OCSP stapling*) test failed. A subsequent transfer to
the same hostname could then succeed if the session ID cache was still fresh, which then skipped the verify status check.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2024-0853?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `curl` | openSUSE:Tumbleweed | All versions | 8.6.0-1.1 |

Products: Haxx Curl.

## How do I fix CVE-2024-0853?

Apply the vendor's patch.

## Is CVE-2024-0853 being exploited?

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

## Other vulnerabilities in Haxx Curl

- [CVE-2026-19931](https://insights.sbomify.com/CVE-2026-19931/): Negotiate ambient user conn reuse (critical 9.8)
- [CVE-2026-10536](https://insights.sbomify.com/CVE-2026-10536/): HTTP/2 stream-dependency tree UAF (critical 9.8)
- [CVE-2026-11856](https://insights.sbomify.com/CVE-2026-11856/): cross-origin Digest auth state leak (critical 9.8)
- [CVE-2026-8925](https://insights.sbomify.com/CVE-2026-8925/): SASL double-free (critical 9.8)
- [CVE-2026-9079](https://insights.sbomify.com/CVE-2026-9079/): stale proxy password leak (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0853 and fix it if it is affected.

What it is: CVE-2024-0853 is a medium-severity vulnerability in Haxx Curl, published on 3 Feb 2024. 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-2024-0853 exists.

Affected product: Haxx Curl. 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-2024-0853/ (Markdown: https://insights.sbomify.com/CVE-2024-0853/index.md)
```

## Sources

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

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