Skip to content
Fencer Intel
medium 6.3

CVE-2026-133706 json

request-filtering-agent before 3.2.2 SSRF Filter Bypass via IPv4-Compatible IPv6 Addresses

published yesterday modified 13h ago also GHSA-rgm6-h343-49v3 , EUVD-2026-131540

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository azu/request-filtering-agent. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
6.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

request-filtering-agent before 3.2.2 contains a server-side request forgery filter bypass because address validation in src/request-filtering-agent.ts treats IPv4-compatible IPv6 addresses in the ::/96 range as public unicast. Attackers controlling a fetched URL can use addresses like ::7f00:1 or ::a9fe:a9fe to reach loopback or link-local services, including cloud metadata endpoints.

Patch / fix

Is CVE-2026-133706 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
13h ago

Exploits and checks

  • github.com https://github.com/azu/request-filtering-agent/security/advisories/GHSA-rgm6-h343-49v3 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 6.3 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
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm request-filtering-agent
<=3.2.1
no fix listed

Affected products

  • azu request-filtering-agent

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of azu/request-filtering-agent published their own advisory on GitHub. Reviewed sources take precedence over it.