Skip to main content
Menu
CVEs

CVE

crw-server request forgery in /v1/scrape endpoint

CVE-2026-130076

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

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 0.45.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.45.1.

Published
Last modified
Reference
Last checked
34/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The fastcrw crw-server software has a server-side request forgery flaw in its /v1/scrape endpoint. Remotely, without logging in, an attacker can supply an unvalidated baseUrl to make the server send requests to loopback or private addresses, and use the returned warnings to learn which internal services are reachable.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

crw-server before 0.45.1 contains a server-side request forgery vulnerability that allows unauthenticated attackers to reach internal services by supplying an unvalidated baseUrl to the /v1/scrape endpoint. Attackers can set llmApiKey and request the summary format, making the server POST to loopback or private addresses and use returned warnings as a reachability oracle.

cve.now Index

34Pcve.now Index 34 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Affects crates.io packages
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 79 if added to CISA KEV
  • Would score about 74 if CISA's SSVC rates exploitation active
  • Would score about 39 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 0.45.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130076 (crw-server before 0.45.1 SSRF via BYOK LLM baseUrl in /v1/scrape), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130076 (entry last updated 2026-11-16):
Affected:
- crates.io package crw-server: fixed in 0.45.1
Fixed versions: 0.45.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130076 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130076 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fastcrw/crw/security/advisories/GHSA-48qx-jg8w-jw4p
- https://github.com/fastcrw/crw/commit/d81ca79b7ef5d558ef8b43221e3afa94c1a7b25e
- https://github.com/fastcrw/crw/releases/tag/v0.45.1
- https://github.com/fastcrw/crw/blob/v0.44.3/crates/crw-crawl/src/single.rs#L2009-L2025
- https://github.com/fastcrw/crw/blob/v0.44.3/crates/crw-server/src/routes/scrape.rs#L56-L60
- https://www.vulncheck.com/advisories/crw-server-before-0.45.1-ssrf-via-byok-llm-baseurl-in-v1-scrape
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130076
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130076"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

Evidence 8

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Patch
  2. Repository
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130076

Is CVE-2026-130076 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-130076?

crw-server (crates.io): before 0.45.1.Source: cve.now feed data

How do I fix CVE-2026-130076?

Upgrade to a fixed version: 0.45.1.Source: cve.now feed data