CVE-2026-5230

HIGHPre-NVD 7.17.1—Trending — 4 sources updated this week

7.1

Improper Access Control, Missing Authorization vulnerability in MIA Technology Inc. Pizzy Library allows Exploiting Incorrectly Configured Access Control Security Levels.

This issue affects Pizzy Library: from 1.0.0.26250 before 1.3.9.26250.

CVSS v3: 7.1
EG Score: 7.1(high)
EPSS: 7.1%
KEV: Not listed

Published

June 15, 2026

Last Modified

June 15, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026

No patch confirmed yet.

generic

T.C. Siber Güvenlik Başkanlığı

https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0383

Vendor Advisories for CVE-2026-5230(1)

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

GHSA-q45q-8hg9-fpfw
GitHub Security AdvisoriesHigh
Improper Access Control, Missing Authorization vulnerability in MIA Technology Inc. Pizzy Library...

Weakness Classification(2)

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-06-16 17:53 UTCEPSS rescore
2026-06-16 15:55 UTCEG score recompute
2026-06-16 15:54 UTCGHSA enrichment
2026-06-16 03:01 UTCEG score recompute
2026-06-16 03:01 UTCGHSA enrichment
2026-06-15 14:08 UTCEG score recompute
2026-06-15 14:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-5230?

CVE-2026-5230 is a high vulnerability published on June 15, 2026. Improper Access Control, Missing Authorization vulnerability in MIA Technology Inc. Pizzy Library allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Pizzy Library: from 1.0.0.26250 before 1.3.9.26250.

When was CVE-2026-5230 disclosed?

CVE-2026-5230 was first published in the National Vulnerability Database on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-5230 actively exploited?

CVE-2026-5230 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-5230?

CVE-2026-5230 has a CVSS v3 base score of 7.1 (NVD).

How do I remediate CVE-2026-5230?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5230, 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-5230

Explore →

Is Your Infrastructure Affected by CVE-2026-5230?

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

Start Free Scan →Browse All CVEs

CVE-2026-5230

📅 Published

🔄 Last Modified

📋 Advisory Details (1)

T.C. Siber Güvenlik Başkanlığı

📣 Vendor Advisories for CVE-2026-5230(1)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)