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


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** BELL-CVE-2025-71436, DEBIAN-CVE-2025-71436, ECHO-2a02-d472-965f, GHSA-m7mm-cj97-2wxq

## What is CVE-2025-71436?

CVE-2025-71436 is a high-severity vulnerability in librdf Raptor RDF Syntax Library, published on 20 Oct 2026. 

### Official description

Raptor RDF Syntax Library from 2.0.15 through 2.0.16 contains a heap-based buffer overflow vulnerability in raptor_new_term_from_counted_literal() 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.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-71436?


## How do I fix CVE-2025-71436?

Upgrade to a fixed version.

## Is CVE-2025-71436 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71436 and fix it if it is affected.

What it is: CVE-2025-71436 is a high-severity vulnerability in librdf Raptor RDF Syntax Library, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71436 exists.

Affected product: librdf Raptor RDF Syntax Library. 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-2025-71436/ (Markdown: https://insights.sbomify.com/CVE-2025-71436/index.md)
```

## Sources

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

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