# CVE-2026-126627: Apache XML Graphics FOP: Temporary files on Unix-like systems are readable by other local users

> Local users can read temporary files created by Apache FOP due to insecure permissions, exposing data; FOP users should upgrade.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-126627, GHSA-77r6-35jh-hcr9, UBUNTU-CVE-2026-126627

## What is CVE-2026-126627?

CVE-2026-126627 is an insecure configuration vulnerability in Apache XML Graphics FOP, published on 11 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Creation of Temporary File With Insecure Permissions vulnerability in Apache XML Graphics FOP.

This issue affects Apache XML Graphics FOP: through 2.11.

Users are recommended to upgrade to version 2.12, which fixes the issue.

Weakness: CWE-378 (Creation of Temporary File With Insecure Permissions)

## Which versions are affected by CVE-2026-126627?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-126627?

No fix has been published for CVE-2026-126627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126627 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126627 and fix it if it is affected.

What it is: CVE-2026-126627 is an insecure configuration vulnerability in Apache XML Graphics FOP, published on 11 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126627 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Apache XML Graphics FOP. 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-2026-126627/ (Markdown: https://insights.sbomify.com/CVE-2026-126627/index.md)
```

## Sources

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

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