CVE-2026-55824

LOWPre-NVD 2.62.6—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% 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
2.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.6Exploit: 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. In versions 4.13.40 through 5.3.46 and 5.7.0-RC1 through 5.7.6, the crawler leaks auth credentials to external hosts. Contao's crawler tries to prevent confidential HTTP client options from being sent to external domains by creating a scoped client: full options for root page origins, cleaned options for everything else. The cleaner removes Cookie and Authorization headers, but it removes the non-Symfony option names basic_auth and bearer_auth instead of Symfony HttpClient's real auth_basic and auth_bearer options. When contao.crawl.default_http_client_options contains Basic or Bearer authentication for a protected staging/production site, those credentials remain in the "clean" client used for external links or configured additional URIs. An attacker who can get an external URL crawled, for example through a link on a crawled page while the broken-link checker is enabled, can receive the crawler credentials. This issue has been fixed in versions 5.3.47 and 5.7.7.

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

Published

July 31, 2026

Last Modified

July 31, 2026

References (1)

Vendor Advisories for CVE-2026-55824(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFixed inDependents
contao/contao5.4.0 ... 5.7.6 (62 versions)5.7.7—
contao/core-bundle5.4.0 ... 5.7.6 (62 versions)5.7.7—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55824?
CVE-2026-55824 is a low vulnerability published on July 31, 2026. Contao is an Open Source CMS. In versions 4.13.40 through 5.3.46 and 5.7.0-RC1 through 5.7.6, the crawler leaks auth credentials to external hosts. Contao's crawler tries to prevent confidential HTTP client options from being sent to external domains by creating a scoped client: full options for…
When was CVE-2026-55824 disclosed?
CVE-2026-55824 was first published in the National Vulnerability Database on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55824 actively exploited?
CVE-2026-55824 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 94.9% of all scored CVEs.
What is the CVSS score of CVE-2026-55824?
CVE-2026-55824 has a CVSS v3 base score of 2.6 (NVD).
How do I remediate CVE-2026-55824?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55824, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55824

Explore →

Is Your Infrastructure Affected by CVE-2026-55824?

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

Start Free Scan →Browse All CVEs