# CVE-2012-6076: Path traversal in n/a

> Local attackers can trick Inkscape into reading unintended EPS files from /tmp, potentially exposing sensitive information.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Mar 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-6076, GHSA-j8fj-6j9g-q9p4

## What is CVE-2012-6076?

CVE-2012-6076 is a medium-severity path traversal vulnerability in n/a, published on 12 Mar 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Inkscape before 0.48.4 reads .eps files from /tmp instead of the current directory, which might cause Inkspace to process unintended files, allow local users to obtain sensitive information, and possibly have other unspecified impacts.

Weakness: CWE-264

## Which versions are affected by CVE-2012-6076?

It affects 1 product.


Products: Inkscape Inkscape.

## How do I fix CVE-2012-6076?

Upgrade to a fixed version.

## Is CVE-2012-6076 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-42704](https://insights.sbomify.com/CVE-2021-42704/): Inkscape Out-of-bounds Write (high 7.8)
- [CVE-2007-1463](https://insights.sbomify.com/CVE-2007-1463/): Memory corruption in n/a (medium 6.8)
- [CVE-2007-1464](https://insights.sbomify.com/CVE-2007-1464/): Other in n/a (medium 6.8)
- [CVE-2026-4980](https://insights.sbomify.com/CVE-2026-4980/): Improper Restriction of XML External Entity Reference in Inkscape (medium 6.3)
- [CVE-2005-3737](https://insights.sbomify.com/CVE-2005-3737/): Memory corruption in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6076 and fix it if it is affected.

What it is: CVE-2012-6076 is a medium-severity path traversal vulnerability in n/a, published on 12 Mar 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-6076 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-2012-6076/ (Markdown: https://insights.sbomify.com/CVE-2012-6076/index.md)
```

## Sources

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

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