# CVE-2013-1424: Memory corruption in matplotlib

> A buffer overflow in matplotlib allows attackers to execute arbitrary code or cause denial of service via crafted input.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jun 2025
- **Updated:** 26 Jun 2025
- **Also known as:** DEBIAN-CVE-2013-1424, GHSA-cv9w-rm27-4w8h, UBUNTU-CVE-2013-1424

## What is CVE-2013-1424?

CVE-2013-1424 is a medium-severity memory corruption vulnerability in matplotlib, published on 26 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow vulnerability in matplotlib.This issue affects matplotlib: before upstream commit ba4016014cb4fb4927e36ce8ea429fed47dcb787.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2013-1424?

It affects 1 product.


Products: Debian Matplotlib.

## How do I fix CVE-2013-1424?

Apply the vendor's patch.

## Is CVE-2013-1424 being exploited?

There is no known exploitation of CVE-2013-1424 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1424 and fix it if it is affected.

What it is: CVE-2013-1424 is a medium-severity memory corruption vulnerability in matplotlib, published on 26 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-1424 in the wild and no public exploit code.

Affected product: matplotlib. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-1424/ (Markdown: https://insights.sbomify.com/CVE-2013-1424/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-1424
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-1424
- OSV: https://osv.dev/vulnerability/CVE-2013-1424

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-1424/
Summaries are generated and may contain mistakes; the official description above is the record.