Security readout for executives and security teams
Plain-English summary
CVE-2025-2691 affects the JavaScript package nossrf before 1.0.4. Its SSRF protection can be bypassed when an attacker supplies a hostname that resolves to local or reserved IP address space. This could let server-side systems reach internal services that should not be exposed.
Executive priority
Treat as a high-priority dependency update for internet-facing or integration-heavy applications. Risk is highest where user-supplied destinations are processed server-side.
Technical view
The issue is CWE-918 SSRF in nossrf. Hostname-based inputs can resolve to local or reserved ranges and bypass the package’s protection logic. The CVSS 4.0 score is 8.8, with network attack vector, low complexity, no privileges, and no user interaction required.
Likely exposure
Organizations are exposed if applications include nossrf versions before 1.0.4, especially where untrusted users can influence URLs, hostnames, webhooks, fetch targets, or proxy destinations.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector includes proof-of-concept exploit maturity, indicating public or practical exploit knowledge may exist.
Researcher notes
Evidence is limited to the CVE data and Snyk reference. Do not assume broader product impact beyond the nossrf package. No cited source in the bundle confirms active exploitation.
Mitigation direction
- Upgrade nossrf to version 1.0.4 or later.
- Review vendor guidance from the Snyk advisory and CVE record.
- Restrict outbound server requests to approved destinations where feasible.
- Add network controls blocking access to internal metadata and reserved address ranges.
Validation and detection
- Search dependency manifests, lockfiles, and SBOMs for nossrf versions before 1.0.4.
- Identify code paths where users control URLs, hostnames, callbacks, or webhook targets.
- Confirm SSRF defenses reject loopback, private, link-local, and reserved resolved addresses.
- Verify upgraded builds deploy the fixed dependency in production artifacts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-2691 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS: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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS: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——snykCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N/E:P3.94.2snykVulnerability scoring details
Base CVSS 4.0 score
8.8HighVector: CVSS: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
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N/E:P
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://security.snyk.io/vuln/SNYK-JS-NOSSRF-9510842CVE reference, snyk
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.