# CVE-2005-0926: Memory corruption in n/a

> Remote attackers can trigger a buffer overflow via malicious MIME attachments, potentially causing crashes or executing arbitrary code.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-0926, GHSA-74wr-9wff-6r75

## What is CVE-2005-0926?

CVE-2005-0926 is a medium-severity memory corruption vulnerability in n/a, published on 29 Mar 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in Sylpheed before 1.0.4 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via attachments with MIME-encoded file names.

## Which versions are affected by CVE-2005-0926?

It affects 1 product.


Products: Sylpheed Sylpheed.

## How do I fix CVE-2005-0926?

Upgrade to a fixed version.

## Is CVE-2005-0926 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3354](https://insights.sbomify.com/CVE-2005-3354/): Memory corruption in n/a (medium 5.1)
- [CVE-2007-1267](https://insights.sbomify.com/CVE-2007-1267/): Security feature bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0926 and fix it if it is affected.

What it is: CVE-2005-0926 is a medium-severity memory corruption vulnerability in n/a, published on 29 Mar 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-0926 in the wild and no public exploit code.

Affected product: n/a. 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-2005-0926/ (Markdown: https://insights.sbomify.com/CVE-2005-0926/index.md)
```

## Sources

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

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