Skip to main content
VulnerabilityPublished

CVE-2026-130076: fastcrw crw · Server-Side Request Forgery (SSRF)

Affects fastcrw crwSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 0.45.1 when convenient.

Data as of 16 Nov 2026, 22:20 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.15.8
Patch
Available – fixed in 0.45.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade fastcrw crw to 0.45.1.

Affected software

ProductAffectedFixed in
fastcrwcrwAffected
  • <0.45.1
Fixed in
  • 0.45.1
crates.iocrwpkg:cargo/crwOther threatsAffected
  • <0.45.1
Fixed in
  • 0.45.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade crw-server to version 0.45.1 or later, where this SSRF vulnerability is fixed. No other mitigation is required as the fix addresses the root cause by validating the baseUrl parameter.

Description

CVE-2026-130076 is a server-side request forgery (SSRF) vulnerability in the fastcrw crw-server before version 0.45.1. It allows unauthenticated attackers to supply an unvalidated baseUrl to the /v1/scrape endpoint, enabling them to make the server send POST requests to internal or private network addresses. The vulnerability can be exploited by setting the llmApiKey and requesting the summary format, which uses returned warnings as a reachability oracle.

References

Community reviews

Loading reviews…