# CVE-2026-107914: Information disclosure in Backdrop

> Attackers can access sensitive configuration archives left on the server due to improper cleanup, potentially exposing system settings.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-rcrw-452r-xvqv

## What is CVE-2026-107914?

CVE-2026-107914 is a high-severity vulnerability in backdropcms Backdrop, published on 9 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Backdrop CMS 1.34 before 1.34.5 and 1.35 before 1.35.1 doesn't sufficiently protect configuration exports when delivering a compressed archive. This vulnerability is mitigated by the fact that an export must have been previously requested by someone with the "Synchronize, import, and export configuration" permission. NOTE: CVE-2026-107914 refers to the vulnerability in which config.admin.inc does not ensure that a file_unmanaged_delete operation occurs. Therefore, many archives could persist: config.tar.gz, config_0.tar.gz, config_1.tar.gz, etc. There is a separate config.module issue that could allow remote access by an anonymous user, but only for the one filename config.tar.gz.

Weakness: CWE-459 (Incomplete Cleanup)

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


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

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

## Is CVE-2026-107914 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107914 is a high-severity vulnerability in backdropcms Backdrop, published on 9 Oct 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-107914 in the wild and no public exploit code.

Affected product: backdropcms Backdrop. 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-107914/ (Markdown: https://insights.sbomify.com/CVE-2026-107914/index.md)
```

## Sources

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

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