CVE-2026-57232

LOWPre-NVD 3.13.1
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.1Exploit: None knownExposed: 0

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

Contao is an Open Source CMS. From 5.3.35 through 5.3.47 and from 5.7.0-RC1 through 5.7.8, the Feed Reader front-end module passes configured RSS feed URLs from FeedReaderController::getResponse() to feedIo->read() without scheme or private-address validation, allowing a backend user with module-edit permissions to make the server request internal network services, loopback addresses, or cloud metadata endpoints. In core-bundle/src/Controller/FrontendModule/FeedReaderController.php, the getResponse() function iterates over the configured feed URLs and passes each one directly to the HTTP client (via $this->feedIo->read($url, new Feed())) with no validation, while the DCA field definition for rss_feed in tl_module.php carries no URL scheme or host validation and the HTTP client is wired as @psr18.http_client (Symfony HttpClient) with no SSRF protection configured, since NoPrivateNetworkHttpClient is not used. This issue is fixed in versions 5.3.48.

CVSS v3
3.1
EG Score
3.1(medium)
EG Risk
14(Track)
EG Risk 14/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
Severity31% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

July 31, 2026

Last Modified

August 3, 2026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 38× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:42 UTCEPSS rescore
  3. 2026-08-28 00:57 UTCEG score recompute
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-24 23:49 UTCEG score recompute
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-21 23:03 UTCEG score recompute
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 22:15 UTCEG score recompute
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 21:22 UTCEG score recompute
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 20:35 UTCEG score recompute
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 19:49 UTCEG score recompute
  25. 2026-08-09 13:46 UTCEPSS rescore
Show 13 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-06 19:03 UTCEG score recompute
  3. 2026-08-06 13:47 UTCEPSS rescore
  4. 2026-08-05 19:17 UTCEPSS rescore
  5. 2026-08-04 15:10 UTCEPSS rescore
  6. 2026-08-04 10:39 UTCEPSS rescore
  7. 2026-08-03 18:18 UTCEG score recompute
  8. 2026-08-03 18:01 UTCEG score recompute
  9. 2026-08-03 10:36 UTCEPSS rescore
  10. 2026-08-02 02:27 UTCEPSS rescore
  11. 2026-07-31 19:23 UTCEG score recompute
  12. 2026-07-31 18:43 UTCEG score recompute
  13. 2026-07-31 18:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57232?
CVE-2026-57232 is a low vulnerability published on July 31, 2026. Contao is an Open Source CMS. From 5.3.35 through 5.3.47 and from 5.7.0-RC1 through 5.7.8, the Feed Reader front-end module passes configured RSS feed URLs from FeedReaderController::getResponse() to feedIo->read() without scheme or private-address validation, allowing a backend user with…
When was CVE-2026-57232 disclosed?
CVE-2026-57232 was first published in the National Vulnerability Database on July 31, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57232 actively exploited?
CVE-2026-57232 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 92.2% of all scored CVEs.
What is the CVSS score of CVE-2026-57232?
CVE-2026-57232 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-57232?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57232, 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-57232

Explore →

Is Your Infrastructure Affected by CVE-2026-57232?

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