Repository metadata tampering via unescaped session names
Published Oct 1, 2026 · Updated Oct 1, 2026
SPARQL injection in 4TU.ResearchData Djehuty before 26.3.2 allows remote authenticated users to alter repository metadata via session editing. The session-update template inserts the name into a DELETE/INSERT query as a safe string, while validation preserves quotes that let the name escape its string literal. A logged-in depositor can write or delete triples in the RDF store shared by all accounts and datasets.
Summary
What happened
SPARQL injection in 4TU.ResearchData Djehuty before 26.3.2 allows remote authenticated users to alter repository metadata via session editing. The session-update template inserts the name into a DELETE/INSERT query as a safe string, while validation preserves quotes that let the name escape its string literal. A logged-in depositor can write or delete triples in the RDF store shared by all accounts and datasets.
The record
- CVE
- CVE-2026-73975
- Published
- Oct 1, 2026
- Updated
- Oct 1, 2026
- Vendor
- 4TU.ResearchData
- Product
- Djehuty
- Classifications
- CWE-943, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 1, 2026CVE publishedPublication date reported by the CVE source.
- Oct 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 26.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Session-name SPARQL injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started