Skip to main content
VulnerabilityPublished

CVE-2026-73976: 4TUResearchData djehuty · Improper Neutralization of Special Elements in Data Query Logic

Affects 4TUResearchData djehutySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 26.3.2 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.3.2
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade djehuty and 4turesearchdata/djehuty to 26.3.2.

Affected software

ProductAffectedFixed in
4TUResearchDatadjehutyAffected
  • <26.3.2
Fixed in
  • 26.3.2
GitHub4turesearchdata/djehutypkg:github/4turesearchdata/djehutyOther threatsAffected
  • <26.3.2
Fixed in
  • 26.3.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability has been officially fixed in djehuty version 26.3.2. Users should upgrade to version 26.3.2 or later to remediate this issue. No additional mitigation is required once the patch is applied.

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.

References

Community reviews

Loading reviews…