A vulnerability has been found in jae-jae fetcher-mcp up to 0.3.9. Impacted is the function fetch_url/fetch_urls of the file /latest/meta-data/iam/security-credentials/ of the component URL Validation. Such manipulation leads to server-side request forgery. It is possible to launch the attack remotely. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-74858
Score 6.3 from GitHub Security Advisory published 2026-08-17. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 17, 2026[BUG] - `fetch_url` and `fetch_urls` allow non-blind SSRF to internal network targets · Issue #37 · jae-jae/fetcher-mcp · GitHub
https://github.com/jae-jae/fetcher-mcp/issues/37GitHub - jae-jae/fetcher-mcp: MCP server for fetch web page content using Playwright headless browser. · GitHub
https://github.com/jae-jae/fetcher-mcp/Vendor Advisories for CVE-2026-74858(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 12:59 UTCEG score recompute
- 2026-08-20 12:59 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:38 UTCGHSA enrichment
- 2026-08-18 14:51 UTCEG score recompute
- 2026-08-18 14:51 UTCGHSA enrichment
- 2026-08-18 13:50 UTCEG score recompute
- 2026-08-18 13:50 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 16:22 UTCEG score recompute
- 2026-08-17 16:10 UTCEG score recompute
- 2026-08-17 16:09 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-74858?
When was CVE-2026-74858 disclosed?
Is CVE-2026-74858 actively exploited?
What is the CVSS score of CVE-2026-74858?
How do I remediate CVE-2026-74858?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74858
Is Your Infrastructure Affected by CVE-2026-74858?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.