A flaw has been found in pdeljanov Symphonia up to 0.6.0. This vulnerability affects unknown code of the component Metadata Handler. This manipulation causes denial of service. The attack needs to be launched locally. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.
CVE-2026-15276
This low-severity CVE scores 3.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- 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
- 3.3
- EG Score
- 3.3(low)
- EPSS
- 2.2%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 10, 2026
References (7)
- cna@vuldbhttps://github.com/pdeljanov/Symphonia/
- cna@vuldbhttps://github.com/pdeljanov/Symphonia/issues/508
- cna@vuldbhttps://github.com/pdeljanov/Symphonia/pull/514
- cna@vuldbhttps://vuldb.com/cve/CVE-2026-15276
- cna@vuldbhttps://vuldb.com/submit/852458
- cna@vuldbhttps://vuldb.com/vuln/377216
- cna@vuldbhttps://vuldb.com/vuln/377216/cti
Vendor Advisories for CVE-2026-15276(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 7× in last 7d / 7× 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-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 20:19 UTCNVD updateCVSS v4 → 1.9
- 2026-07-10 18:57 UTCMITRE cvelistV5CVSS v4 → 4.8
- 2026-07-09 23:47 UTCNVD updateCVSS v4 → 1.9
- 2026-07-09 22:10 UTCEG score recompute
- 2026-07-09 22:10 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-404
- CVE-2018-8639NVD 7.8EG 9.0 KEVEPSS 97%HIGH
- CVE-2018-8611NVD 7.8EG 9.0 KEVEPSS 90%HIGH
- CVE-2018-8453NVD 7.8EG 9.0 KEVEPSS 99%HIGH
- CVE-2018-8406NVD 7.8EG 9.0 KEVHIGH
- CVE-2018-8405NVD 7.8EG 9.0 KEVHIGH
- CVE-2018-8120NVD 7.0EG 9.0 KEVEPSS 99%HIGH
- CVE-2017-6627NVD 7.5EG 9.0 KEVEPSS 93%HIGH
- CVE-2018-8450EG 8.8EPSS 97%HIGH
- CVE-2019-1708EG 8.6HIGH
- CVE-2019-1706EG 8.6HIGH
Frequently asked(5)
What is CVE-2026-15276?
When was CVE-2026-15276 disclosed?
Is CVE-2026-15276 actively exploited?
What is the CVSS score of CVE-2026-15276?
How do I remediate CVE-2026-15276?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15276
Is Your Infrastructure Affected by CVE-2026-15276?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.