How severe is CVE-2025-57814?

No CVSS score has been assigned to CVE-2025-57814 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-57814?

CVE-2025-57814 affects the following packages: request-filtering-agent (npm). Ecosystems affected: npm.

How do I fix CVE-2025-57814?

Update request-filtering-agent to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-57814 is resolved across your whole dependency graph.

How do I detect CVE-2025-57814 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for request-filtering-agent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-57814 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2025-57814 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-57814 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-57814?

CVE-2025-57814 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-57814?

CVE-2025-57814 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-57814 published, and has it been updated?

CVE-2025-57814 was published on August 25, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2025-57814 — request-filtering-agent

CVE-2025-57814 is a Server-Side Request Forgery (SSRF) vulnerability in request-filtering-agent. A fix is available for request-filtering-agent — see the affected versions and patch details below.

request-filtering-agent SSRF Bypass via HTTPS Requests

Also known asGHSA-pw25-c82r-75mm

Published

Aug 25, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-57814.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

22other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

request-filtering-agentnpm

129Kdownloads / week

Description

request-filtering-agent versions 1.x.x and earlier contain a vulnerability where HTTPS requests to 127.0.0.1 bypass IP address filtering, while HTTP requests are correctly blocked.

Impact:

Vulnerable patterns (requests that should be blocked but are allowed):

https://127.0.0.1:443/api
https://127.0.0.1:8443/admin
Any HTTPS request using direct IP address https://127.0.0.1

This vulnerability primarily affects services using self-signed certificates on 127.0.0.1.

Not affected (correctly blocked in all versions):

http://127.0.0.1:80/api - HTTP requests are properly blocked
https://localhost:443/api - Domain-based requests trigger DNS lookup and are blocked
http://localhost:80/api - Domain-based HTTP requests are blocked
Requests to other private IPs like 192.168.x.x, 10.x.x.x, 172.16.x.x

This allows attackers to potentially access internal HTTPS services running on localhost, bypassing the library's SSRF protection. The vulnerability is particularly dangerous when the application accepts user-controlled URLs and internal services are only protected by network-level restrictions.

Fixed in 2.0.0

This vulnerability has been fixed in request-filtering-agent version 2.0.0. Users should upgrade to version 2.0.0 or later.

Root Cause:The HTTPS agent fails to validate direct IP addresses like https://127.0.0.1 during TLS connection setup, allowing them to bypass the security filter.

Details: https://github.com/azu/request-filtering-agent-https127-test

Thanks Luca

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`request-filtering-agent`	all versions	2.0.0`npm install request-filtering-agent@2.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for request-filtering-agent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update request-filtering-agent to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-57814 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

request-filtering-agent versions 1.x.x and earlier contain a vulnerability where HTTPS requests to 127.0.0.1 bypass IP address filtering, while HTTP requests are correctly blocked. **Impact:** Vulnerable patterns (requests that should be blocked but are allowed): - https://127.0.0.1:443/api - https://127.0.0.1:8443/admin - Any HTTPS request using direct IP address `https://127.0.0.1` This vulnerability primarily affects services using self-signed certificates on `127.0.0.1`. **Not affected (correctly blocked in all versions):** - http://127.0.0.1:80/api - HTTP requests are properly blocked

O3 Security · Impact-Aware SCA

Is CVE-2025-57814 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works