[From nobody Sun Oct 18 00:37:07 2026
Received: (at submit) by bugs.debian.org; 20 Aug 2026 18:36:27 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-11.0 required=4.0 tests=BAYES_00,FROMDEVELOPER,
 MD5_SHA1_SUM,NO_RELAYS,XMAILER_REPORTBUG autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 23; hammy, 148; neutral, 50; spammy,
 2. spammytokens:0.940-+--H*r:bugs.debian.org, 0.931-+--confidential
 hammytokens:0.000-+--XDebbugsCc, 0.000-+--X-Debbugs-Cc,
 0.000-+--H*F:U*carnil, 0.000-+--H*Ad:N*Bug, 0.000-+--HTo:N*Debian
Return-path: <carnil@debian.org>
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from <carnil@debian.org>) id 1wx7cn-006N5w-2K
 for submit@bugs.debian.org; Thu, 20 Aug 2026 18:36:27 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso <carnil@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: rdf4j: CVE-2018-1000644
Message-ID: <178725098474.4001212.2954557289539562486.reportbug@eldamar.lan>
X-Mailer: reportbug 13.2.0+nmu1
Date: Thu, 20 Aug 2026 20:36:24 +0200
Delivered-To: submit@bugs.debian.org

Source: rdf4j
Version: 3.7.7+ds-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/eclipse-rdf4j/rdf4j/issues/1056
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>

Hi,

The following vulnerability was published for rdf4j.

CVE-2018-1000644[0]:
| Eclipse RDF4j version < 2.4.0 Milestone 2 contains a XML External
| Entity (XXE) vulnerability in RDF4j XML parser parsing RDF files
| that can result in the disclosure of confidential data, denial of
| service, server side request forgery, port scanning. This attack
| appear to be exploitable via Specially crafted RDF file.

Please note that the issue recently got a second CVE assigned,
CVE-2026-15803 for an incomplete fix of the original CVE-2018-1000644.
So once fixing this issue, make sure to fix it completely following
[3].

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-1000644
    https://www.cve.org/CVERecord?id=CVE-2018-1000644
[1] https://github.com/eclipse-rdf4j/rdf4j/issues/1056
[2] https://github.com/eclipse-rdf4j/rdf4j/commit/50f2f51950227a4ec595a2922d81da487aba5135
[3] https://gitlab.eclipse.org/security/cve-assignment/-/work_items/175

Regards,
Salvatore
]