CVE-2025-2691Public exploitNetwork attack vector

Internal-resource access via hostname validation bypass

Published Mar 23, 2025 · Updated Aug 3, 2026

SSRF in nossrf before 1.0.4 allows remote attackers to reach local or reserved addresses through applications that validate attacker-supplied URLs. The asyncValidateUrl API approves a test hostname as safe even though DNS resolves it to 127.0.0.1, so hostname validation does not enforce the resolved-address boundary. Exploitation requires a consuming application to pass attacker-controlled hostnames to this API and then act on the result, enabling unauthorized requests to internal services and limited data access or modification.

CVSS severity8.2
High
EPSS probability0.38%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

SSRF in nossrf before 1.0.4 allows remote attackers to reach local or reserved addresses through applications that validate attacker-supplied URLs. The asyncValidateUrl API approves a test hostname as safe even though DNS resolves it to 127.0.0.1, so hostname validation does not enforce the resolved-address boundary. Exploitation requires a consuming application to pass attacker-controlled hostnames to this API and then act on the result, enabling unauthorized requests to internal services and limited data access or modification.

The record

CVE
CVE-2025-2691
Published
Mar 23, 2025
Updated
Aug 3, 2026
Vendor
Nossrf Project
Product
nossrf
Classifications
CWE-918, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 23, 2025CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <1.0.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Nossrf Project · nossrfversion=0 <1.0.4

Published CVSS scores

8.2SnykCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
9.1NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
7.8SnykCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo