CVE-2024-24267

HIGHNVD 7.57.5—Elevated

7.5

gpac v2.2.1 (fixed in v2.4.0) was discovered to contain a memory leak via the gfio_blob variable in the gf_fileio_from_blob function.

CVSS v3: 7.5
EG Score: 7.5(medium)
EPSS: 59.8%
KEV: Not listed

Published

February 5, 2024

Last Modified

September 26, 2025

References (7)

cve@mitrehttps://github.com/NixOS/nixpkgs/pull/305402
cve@mitrehttps://github.com/gpac/gpac/commit/d28d9ba45cf4f628a7b2c351849a895e6fcf2234
cve@mitrehttps://github.com/gpac/gpac/issues/2571
cve@mitrehttps://github.com/yinluming13579/gpac_defects/blob/main/gpac_3.md
af854a3a-2127-422b-91ae-364da2661108https://github.com/gpac/gpac/commit/d28d9ba45cf4f628a7b2c351849a895e6fcf2234
af854a3a-2127-422b-91ae-364da2661108https://github.com/gpac/gpac/issues/2571
af854a3a-2127-422b-91ae-364da2661108https://github.com/yinluming13579/gpac_defects/blob/main/gpac_3.md

Weakness Classification(1)

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

CWE-401Missing Release of Memory after Effective Lifetime (Memory Leak)

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-04 13:11 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-26 13:43 UTCepss_batch

Frequently asked(5)

What is CVE-2024-24267?

CVE-2024-24267 is a high vulnerability published on February 5, 2024. gpac v2.2.1 (fixed in v2.4.0) was discovered to contain a memory leak via the gfioblob variable in the gffileiofromblob function.

When was CVE-2024-24267 disclosed?

CVE-2024-24267 was first published in the National Vulnerability Database on February 5, 2024, with the most recent update on September 26, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2024-24267 actively exploited?

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

What is the CVSS score of CVE-2024-24267?

CVE-2024-24267 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2024-24267?

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

Explore →

Is Your Infrastructure Affected by CVE-2024-24267?

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

Start Free Scan →Browse All CVEs

CVE-2024-24267

📅 Published

🔄 Last Modified

🔗 References (7)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2024-24267?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (7)

Frequently asked(5)

Related CVEs(same CWE)