# CVE-2026-118371: LibreSSL through 4.4.0 CRLF Injection via OCSP_sendreq_new() Request Line


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-p83x-c6v7-9mxw

## What is CVE-2026-118371?

CVE-2026-118371 is a medium-severity vulnerability in OpenBSD LibreSSL, published on 28 Oct 2026. 

### Official description

LibreSSL through 4.4.0 contains a CRLF injection vulnerability in the libcrypto OCSP_sendreq_new() and OCSP_parse_url() functions, which write unvalidated request paths into the OCSP POST request line. Attackers can embed carriage return and line feed characters in a certificate's Authority Information Access OCSP URI to inject HTTP headers or split requests sent to responders and proxies.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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


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

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

## Is CVE-2026-118371 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118371 is a medium-severity vulnerability in OpenBSD LibreSSL, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118371 in the wild and no public exploit code.

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

## Sources

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

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