CVE-2026-72574

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreHIGH confidence

Score 6.1 from GitHub Security Advisory published 2026-08-10. a secondary CVSS source baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A host header injection vulnerability in picocms/Pico through 2.1.4 allows an unauthenticated remote attacker to control the origin of JavaScript and CSS assets loaded by the default theme. When base_url is unset (the default), Pico::getBaseUrl in lib/Pico.php builds the base URL from unvalidated Host, X-Forwarded-Host, X-Forwarded-Proto, and X-Forwarded-Port request headers.

CVSS v3
6.1
EG Score
6.1(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 computed
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 10, 2026

Advisory Details (3)

Auto-updated Aug 10, 2026
No patch confirmed yet.
generic

Pico/lib/Pico.php at master · picocms/Pico · GitHub

https://github.com/picocms/Pico/blob/master/lib/Pico.php
generic

GitHub - picocms/Pico: Pico is a stupidly simple, blazing fast, flat file CMS. · GitHub

https://github.com/picocms/Pico
generic

Pico - A stupidly simple, blazing fast, flat file CMS.

https://picocms.org

Vendor Advisories for CVE-2026-72574(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 25× in last 7d / 41× 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.

  1. 2026-08-21 07:06 UTCEG score recompute
  2. 2026-08-21 07:06 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 08:14 UTCEG score recompute
  5. 2026-08-20 08:14 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 09:21 UTCEG score recompute
  8. 2026-08-19 09:21 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 10:28 UTCEG score recompute
  12. 2026-08-18 10:28 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 11:35 UTCEG score recompute
  15. 2026-08-17 11:35 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 12:43 UTCEG score recompute
  19. 2026-08-16 12:43 UTCGHSA enrichment
  20. 2026-08-16 02:15 UTCEPSS rescore
  21. 2026-08-15 13:51 UTCEG score recompute
  22. 2026-08-15 13:51 UTCGHSA enrichment
  23. 2026-08-15 01:31 UTCEPSS rescore
  24. 2026-08-14 14:58 UTCEG score recompute
  25. 2026-08-14 14:58 UTCGHSA enrichment
Show 16 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 16:05 UTCGHSA enrichment
  3. 2026-08-12 17:13 UTCEG score recompute
  4. 2026-08-12 17:13 UTCGHSA enrichment
  5. 2026-08-12 13:51 UTCEPSS rescore
  6. 2026-08-11 18:20 UTCEG score recompute
  7. 2026-08-11 18:20 UTCGHSA enrichment
  8. 2026-08-10 19:28 UTCEG score recompute
  9. 2026-08-10 19:28 UTCGHSA enrichment
  10. 2026-08-10 18:35 UTCEG score recompute
  11. 2026-08-10 18:35 UTCGHSA enrichment
  12. 2026-08-10 12:23 UTCEG score recompute
  13. 2026-08-10 12:02 UTCEG score recompute
  14. 2026-08-10 11:20 UTCEG score recompute
  15. 2026-08-10 10:57 UTCEG score recompute
  16. 2026-08-10 10:56 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72574?
CVE-2026-72574 is a medium vulnerability published on August 10, 2026. A host header injection vulnerability in picocms/Pico through 2.1.4 allows an unauthenticated remote attacker to control the origin of JavaScript and CSS assets loaded by the default theme. When base_url is unset (the default), Pico::getBaseUrl in lib/Pico.php builds the base URL from unvalidated…
When was CVE-2026-72574 disclosed?
CVE-2026-72574 was first published in the National Vulnerability Database on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72574 actively exploited?
CVE-2026-72574 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.5% of all scored CVEs.
What is the CVSS score of CVE-2026-72574?
CVE-2026-72574 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-72574?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72574, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72574

Explore →

Is Your Infrastructure Affected by CVE-2026-72574?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.