CVE-2025-2691: Nossrf Nossrf Server-Side Request Forgery (SSRF) Vulnerability

HIGH
Advisory Identifier: GHSA-vm77-mr48-27wj
CVSS 8.2
CWE-918
Published
Advisory Summary

CVE-2025-2691 is a HIGH (CVSS 8.2) nossrf server-side request forgery (ssrf) vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Nossrf libraries in the npm ecosystem. The issue involves nossrf server-side request forgery (ssrf). Remediation is available by upgrading affected packages to version 1.0.4.

CVE-2025-2691 at a Glance

CVE Identifier CVE-2025-2691
GHSA Identifier GHSA-vm77-mr48-27wj
Severity HIGH
CVSS v3.1 Base Score 8.2
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Nossrf
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2025-2691

To remediate this vulnerability, upgrade all affected Nossrf dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nossrf fixed: 1.0.4
npm install nossrf@1.0.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls nossrf

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-2691, inspect your project dependencies using npm:

npm ls nossrf

Analyze the terminal output to locate any version of Nossrf in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.4), your application is affected.

Note: The npm ls nossrf command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Nossrf, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Versions of the package nossrf before 1.0.4 are vulnerable to Server-Side Request Forgery (SSRF), where an attacker can provide a hostname that resolves to a local or reserved IP address space and bypass the SSRF protection mechanism.

CVE-2025-2691 Affected Nossrf Versions

1 component(s)
Fixed Versions:
1.0.4
Product / Package Ecosystem Affected Versions Fixed Version
nossrf
npm
< 1.0.4
1.0.4

References

Frequently Asked Questions

What is CVE-2025-2691?
CVE-2025-2691 is a security vulnerability in Nossrf involving nossrf Server-Side Request Forgery (SSRF) under CWE-918: Server-Side Request Forgery (SSRF).
Which Nossrf versions are affected?
Affected versions include releases prior to 1.0.4 across affected packages: nossrf.
What version fixes CVE-2025-2691?
Upgrading to 1.0.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nossrf affected?
Yes, nossrf is affected in releases prior to 1.0.4. Upgrade your dependency to 1.0.4 or later.
What is the CVSS score of CVE-2025-2691?
CVE-2025-2691 has a CVSS v3.1 base score of 8.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N.
What CWE is associated with CVE-2025-2691?
CVE-2025-2691 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check npm dependencies for CVE-2025-2691?
Run the dependency tree command: 'npm ls nossrf'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vm77-mr48-27wj",
  "modified" : "2025-09-26T21:27:59Z",
  "published" : "2025-03-23T15:30:33Z",
  "aliases" : [ "CVE-2025-2691" ],
  "summary" : "nossrf Server-Side Request Forgery (SSRF)",
  "details" : "Versions of the package nossrf before 1.0.4 are vulnerable to Server-Side Request Forgery (SSRF), where an attacker can provide a hostname that resolves to a local or reserved IP address space and bypass the SSRF protection mechanism.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N"
  }, {
    "type" : "CVSS_V4",
    "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "nossrf"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.0.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-2691"
  }, {
    "type" : "WEB",
    "url" : "https://security.snyk.io/vuln/SNYK-JS-NOSSRF-9510842"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-03-25T16:30:30Z",
    "nvd_published_at" : "2025-03-23T15:15:13Z"
  }
}