# CVE-2026-53534: JabRef CAYW Sublime Text integration permits operating-system command injection

> Attackers can execute arbitrary OS commands via the built-in HTTP server if enabled, requiring user interaction and specific configuration.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** No
- **Published:** 17 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-m42c-cw93-p629, UBUNTU-CVE-2026-53534

## What is CVE-2026-53534?

CVE-2026-53534 is a high-severity command injection vulnerability in jabref, published on 17 Sep 2026. 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

JabRef is a desktop application for managing BibTeX and BibLaTeX libraries. Prior to 6.0-alpha.6, when jabsrv or JabRef's built-in HTTP server is enabled, the GET /better-bibtex/cayw endpoint accepts an external command query parameter and CAYWQueryParams.getCommand() passes it through CAYWResource.getCitation() into PushToSublimeText.getCommandLine(). On Unix-like systems, PushToSublimeText combines this untrusted cite-command prefix and citation keys into a string executed through sh -c by ProcessBuilder without shell escaping. A client that can cause a localhost request with application=sublime can inject shell metacharacters and execute operating-system commands as the JabRef user when a valid Sublime Text command path is configured and the victim completes the CAYW selection dialog. The built-in server is disabled by default, so exploitation requires the victim to enable it or run jabsrv. This issue is fixed in version 6.0-alpha.6.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-53534 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53534 is a high-severity command injection vulnerability in jabref, published on 17 Sep 2026. 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-2026-53534 in the wild and no public exploit code.

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

## Sources

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

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