Skip to main content
CVE-2026-133706VulnerabilityPublished

request-filtering-agent before 3.2.2 contains a server-side request forgery filter bypass because address validation

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133706· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.2.2 when convenient.

Data as of 20 Nov 2026, 16:22 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.3
CNA (VulnCheck)CVSS 3.13.7
Patch
Available – fixed in 3.2.2
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade request-filtering-agent to 3.2.2.

Affected software

ProductAffectedFixed in
azurequest-filtering-agentAffected
  • <3.2.2
Fixed in
  • 3.2.2
npmrequest-filtering-agentpkg:npm/request-filtering-agentOther threatsAffected
  • <3.2.2
Fixed in
  • 3.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in request-filtering-agent version 3.2.2 and later. Users should upgrade to version 3.2.2 or newer to remediate this vulnerability. No other mitigation actions are indicated.

Description

A server-side request forgery (SSRF) filter bypass exists in request-filtering-agent versions before 3.2.2. The vulnerability arises because the address validation logic incorrectly treats IPv4-compatible IPv6 addresses in the ::/96 range as public unicast addresses. This allows attackers controlling a fetched URL to use specially crafted IPv6 addresses to access internal loopback or link-local services, including sensitive cloud metadata endpoints.

References

Community reviews

Loading reviews…