A security vulnerability has been detected in agentejo Cockpit CMS up to 0.12.2. Affected by this issue is the function Spyc::YAMLLoad of the file /config/config.yaml of the component htaccess Handler. Such manipulation leads to files or directories accessible. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. Configuration settings should be changed. The vendor was contacted early about this disclosure but did not respond in any way.
CVE-2026-13533
Score 5.3 from GitHub Security Advisory published 2026-06-29. a secondary CVSS source baseline 5.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
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 55(Attend)EG Risk 55/100SSVC: Attend
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 computedSeverity53% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 20.8%
- KEV
- Not listed
Published
June 29, 2026
Last Modified
June 29, 2026
Advisory Details (1)
Auto-updated Jun 29, 2026Cockpit CMS v1 Unauthenticated config.yaml Disclosure — CWE-552 (5.4k stars, unmaintained, 0day) · GitHub
https://gist.github.com/nov-1337/3eb0a06c602ced9c3b11b675b53947daVendor Advisories for CVE-2026-13533(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 50× 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-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 20:18 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-15 22:02 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 23:45 UTCGHSA enrichment
- 2026-07-14 01:30 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-13 03:15 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 04:58 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 06:43 UTCGHSA enrichment
- 2026-07-10 08:28 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 10:13 UTCGHSA enrichment
- 2026-07-08 15:15 UTCEPSS rescore
Show 25 moreShow fewer
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 11:58 UTCGHSA enrichment
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:43 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 15:28 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 17:12 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 18:56 UTCGHSA enrichment
- 2026-07-03 20:40 UTCGHSA enrichment
- 2026-07-02 22:24 UTCGHSA enrichment
- 2026-07-02 00:09 UTCGHSA enrichment
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 01:54 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 03:38 UTCGHSA enrichment
- 2026-06-29 17:26 UTCNVD updateCVSS v4 → 5.5
- 2026-06-29 16:13 UTCMITRE cvelistV5CVSS v4 → 6.9
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 08:04 UTCNVD updateCVSS v4 → 5.5
- 2026-06-29 05:19 UTCEG score recompute
- 2026-06-29 05:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-425 · CWE-552
- CVE-2018-3774EG 10.0CRITICAL
- CVE-2019-25709EG 9.8CRITICAL
- CVE-2019-12768EG 9.8CRITICAL
- CVE-2019-19843EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2018-18922EG 9.8CRITICAL
- CVE-2018-19207EG 9.8EPSS 100%CRITICAL
- CVE-2017-17736EG 9.8EPSS 99%CRITICAL
- CVE-2018-6624EG 9.8CRITICAL
- CVE-2018-10867EG 9.1CRITICAL
Frequently asked(5)
What is CVE-2026-13533?
When was CVE-2026-13533 disclosed?
Is CVE-2026-13533 actively exploited?
What is the CVSS score of CVE-2026-13533?
How do I remediate CVE-2026-13533?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-13533
Is Your Infrastructure Affected by CVE-2026-13533?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.