CVE-2025-71436: Raptor RDF Syntax Library 2.0.15 through 2.0.16 Heap Buffer Overflow via Language Tag

Published Oct 20, 2026
·
Updated

(Raptor RDF Syntax Library from 2.0.15 through 2.0.16 contains a heap-b ...)

Other sources

Raptor RDF Syntax Library from 2.0.15 through 2.0.16 contains a heap-based buffer overflow vulnerability in raptornewtermfromcountedliteral() caused by truncating language tag length to an unsigned char. Attackers can supply Turtle, TriG, N-Triples or N-Quads documents with language tags of 256 bytes or longer to corrupt heap memory, crash applications, and possibly execute code.

— MITRE

Affected Software

12 affected components
Raptor RDF Syntax Library>=2.0.15<=2.0.16
debian/raptor2*
debian/raptor2*
debian/raptor2*
debian/raptor2<=2.0.15-4+deb12u1, <=2.0.16-6, <=2.0.16-7
ubuntu/raptor2*
ubuntu/raptor2*
ubuntu/raptor2*
ubuntu/raptor2*
ubuntu/raptor2*
ubuntu/raptor2*
ubuntu/raptor2*

Event History

Oct 20, 2026
CVE Published
via MITRE·03:40 PM
Data Sourced
via MITRE·03:40 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·03:54 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeakness
Oct 29, 2026
Data Sourced
via OSV·09:47 AM
Affected Software

Frequently Asked Questions

1

Which deployments are exposed?

Deployments using Raptor RDF Syntax Library versions 2.0.15 through 2.0.16 are exposed when they parse Turtle, TriG, N-Triples, or N-Quads documents containing language-tagged literals.

2

What must an attacker provide to trigger the flaw?

An attacker needs to cause the application to parse a supported RDF document with a language tag that is 256 bytes or longer. No authentication or special privileges are indicated by the supplied severity vector, but user interaction is required.

3

How can I assess whether an application is at immediate risk?

Check whether the application uses Raptor 2.0.15 or 2.0.16 and accepts or processes RDF documents from untrusted sources. Inputs using the affected syntaxes should be reviewed for language tags of 256 bytes or more.

4

What can be done if updating is not immediately possible?

Reject or sanitize Turtle, TriG, N-Triples, and N-Quads inputs containing language tags of 256 bytes or longer before they reach the vulnerable parser. This specifically removes the documented trigger condition.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203