# CVE-2026-73976: djehuty: Unauthenticated SPARQL injection in the search API (`order`, `operator`, `key`)

> Unauthenticated attackers can inject SPARQL queries to exfiltrate private data or cause denial of service in the djehuty research data repository.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/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:** 1 Oct 2026
- **Also known as:** GHSA-7gp2-rxw9-vw6p

## What is CVE-2026-73976?

CVE-2026-73976 is a high-severity 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 unauthenticated attacker can inject SPARQL into the search/listing queries through three separate parameters. Because the affected queries are read (SELECT) queries, this does not write to the store, but it allows: Cross-graph data exfiltration — e.g. UNION-ing in triples from graphs the request was never scoped to (drafts/private/internal data held in the RDF store); denial of service — expensive or malformed queries that tie up the SPARQL backend / web workers. No account or user interaction is required. 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-73976?


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

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

## Is CVE-2026-73976 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73976 is a high-severity 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-73976 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-73976/ (Markdown: https://insights.sbomify.com/CVE-2026-73976/index.md)
```

## Sources

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

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