# CVE-2026-116620: Tencent RapidJSON Regex stream.h Take out-of-bounds


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** AZL-111134, DEBIAN-CVE-2026-116620, GHSA-xfhf-c35f-773q, UBUNTU-CVE-2026-116620

## What is CVE-2026-116620?

CVE-2026-116620 is a medium-severity vulnerability in Tencent RapidJSON, published on 27 Oct 2026. 

### Official description

A security vulnerability has been detected in Tencent RapidJSON up to 1.1.0. This issue affects the function GenericStringStream<UTF8<char>>::Take in the library include/rapidjson/stream.h of the component Regex Parser. The manipulation leads to out-of-bounds read. The attack can be initiated remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-116620?


## How do I fix CVE-2026-116620?

No fix has been published for CVE-2026-116620 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116620 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116620 and fix it if it is affected.

What it is: CVE-2026-116620 is a medium-severity vulnerability in Tencent RapidJSON, published on 27 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116620 exists.

Affected product: Tencent RapidJSON. 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-2026-116620/ (Markdown: https://insights.sbomify.com/CVE-2026-116620/index.md)
```

## Sources

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

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