# CVE-2026-73975: djehuty: Authenticated SPARQL injection in session editing allows writing arbitrary RDF triples

> Authenticated attackers can inject SPARQL via session names to modify or delete arbitrary RDF triples, compromising repository-wide metadata integrity.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-9864-23x8-762h

## What is CVE-2026-73975?

CVE-2026-73975 is a high-severity code injection vulnerability in 4TUResearchData djehuty, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

djehuty is a research data repository system developed by 4TU.ResearchData. Prior to version 26.3.2, an authenticated depositor can inject arbitrary SPARQL into a state-modifying (DELETE/INSERT) query by supplying a crafted session name, letting them write (and delete) arbitrary triples anywhere in the RDF store. Because the RDF store is shared across all accounts and datasets, this is an integrity compromise of the whole repository's metadata, not just the attacker's own records. Having a logged-in account is a precondition. djehuty allows self-registration via ORCID/SAML, so this is a low barrier in typical deployments. This issue has been patched in version 26.3.2.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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


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

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

## Is CVE-2026-73975 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73975 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73975 is a high-severity code injection vulnerability in 4TUResearchData djehuty, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73975 exists.

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

## Sources

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

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