Read the docs
TI-2020-06190 Aliases CVE-2020-7670

agoo prior to 2.14.0 allows request smuggling attacks where agoo is used as a backend and…

Priority LOW 35CWE-444Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA.

Summary

agoo prior to 2.14.0 allows request smuggling attacks where agoo is used as a backend and a frontend proxy also being vulnerable. HTTP pipelining issues and request smuggling attacks might be possible due to incorrect Content-Length and Transfer encoding header parsing. It is possible to conduct HTTP request smuggling attacks where `agoo` is used as part of a chain of backend servers due to insufficient `Content-Length` and `Transfer Encoding` parsing.

Why it matters now

EPSS 0.0117 67th percentileScored 2026-11-07
Fix Fixed agoo: 2.14.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—agoobefore 2.14.02.14.0Patch availableCNA
  • agoo Vendor— Affected before 2.14.0 Fixed in 2.14.0 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:ohler:agoo:*:*:*:*:*:ruby:*:*up to 2.12.3VulnerableOhler
  • cpe:2.3:a:ohler:agoo:*:*:*:*:*:ruby:*:* Versions up to 2.12.3 Vulnerable ·Ohler

Remediation

  • Fix · CNA agoo Fixed in 2.14.0

Timeline

  1. 2026-10-02 Threatist record created from CVE-2020-7670

References

Other 2

  • TI-2022-12525 Agoo before 2.14.3 does not reject GraphQL fragment spreads that form cycles, leading to… CVSS 3.1HIGH 7.5

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences