Skip to main content
VulnerabilityPublished

CVE-2026-133706: azu request-filtering-agent · Server-Side Request Forgery (SSRF)

Affects azu request-filtering-agentSource CVE Database V5

0
Compare

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

Data as of 20 Nov 2026, 13:04 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 azu 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

Upgrade the azu request-filtering-agent to version 3.2.2 or later, where this SSRF filter bypass vulnerability has been fixed. No other mitigation is necessary once the official fix is applied.

Description

A Server-Side Request Forgery (SSRF) vulnerability exists in azu request-filtering-agent versions before 3.2.2. The flaw arises because the address validation logic incorrectly treats IPv4-compatible IPv6 addresses in the ::/96 range as public unicast, allowing attackers to bypass filters. This enables attackers controlling a fetched URL to access internal loopback or link-local services, including sensitive cloud metadata endpoints.

References

Community reviews

Loading reviews…