# Improper Neutralization of CRLF Sequences in HTTP Headers in Jooby ('HTTP Response Splitting)

Advisory record · `GHSA-gv3v-92v6-m48j`

- **Identifiers:** `GHSA-gv3v-92v6-m48j` · `CVE-2020-7622` · `SNYK-JAVA-IOJOOBY-564249`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-444](https://cwe.mitre.org/data/definitions/444.html)
- **Tags:** [HTTP request smuggling](https://agentprime.io/advisories/tag/request-smuggling.md)
- **Published:** 3 Apr 2020
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 3 Apr 2020, 15:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `io.jooby:jooby-netty` (Maven): affected `<2.2.1`; fixed in `2.2.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Jooby's jooby-netty module, versions before 2.2.1, is vulnerable to HTTP response splitting through CRLF sequences in HTTP headers. An attacker who can get user-supplied data into response headers could inject extra headers or content, which the advisory links to cross-site scripting, cache poisoning, and page hijacking. Upgrade to jooby-netty 2.2.1 or later. If upgrading is not possible, make sure user-supplied data cannot flow into HTTP headers, or strip CRLF characters from it first.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`, from CNA (snyk)

- **CISA KEV:** Not listed.
- **EPSS:** 0.016, the 75th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:18 UTC: First seen by agentprime
- 31 Oct 2026, 14:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-gv3v-92v6-m48j)

## Sources

- [GitHub Advisory Database: GHSA-gv3v-92v6-m48j](https://github.com/advisories/GHSA-gv3v-92v6-m48j)
- [OSV: GHSA-gv3v-92v6-m48j](https://osv.dev/vulnerability/GHSA-gv3v-92v6-m48j)
- <https://github.com/jooby-project/jooby/security/advisories/GHSA-gv3v-92v6-m48j>
- <https://nvd.nist.gov/vuln/detail/CVE-2020-7622>
- <https://github.com/jooby-project/jooby/commit/b66e3342cf95205324023cfdf2cb5811e8a6dcf4>
- <https://snyk.io/vuln/SNYK-JAVA-IOJOOBY-564249>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gv3v-92v6-m48j>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gv3v-92v6-m48j/>. Everything for agents: <https://agentprime.io/llms.txt>.