CVSS 4.0
5.5 mediumCVSS: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:PMedium (5.5) in tencent rapidjson. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
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:PCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExplain CVE-2026-116620 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116620?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116620?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116620 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Tencent RapidJSON | 1.0 |
| Tencent RapidJSON | 1.1.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | rapidjson | no fix listed | DEBIAN-CVE-2026-116620 |
| Ubuntu | 26.04:LTS, 26.10, Pro:16.04:LTS and 4 more | rapidjson | no fix listed | UBUNTU-CVE-2026-116620 |
| Red Hat | enterprise_linux:9::appstream | mecab, mecab-devel, mecab-debuginfo and 1 more | 0:0.996-3.module+el9.9.0+24089+64aac046.4 | RHSA-2026:99741 |
| Red Hat | enterprise_linux:9::appstream | mecab-ipadic, mecab-ipadic-EUCJP | 0:2.7.0.20070801-24.module+el9.9.0+24089+64aac046 | RHSA-2026:99741 |
| Red Hat | enterprise_linux:9::appstream | mysql, mysql-libs, mysql-test and 11 more | 0:8.4.13-1.module+el9.9.0+25300+c0fc77bc | RHSA-2026:99741 |
| Red Hat | enterprise_linux:9::appstream | perl-DBD-MySQL, perl-DBD-MySQL-debuginfo, perl-DBD-MySQL-debugsource | 0:4.053-3.module+el9.9.0+24089+64aac046 | RHSA-2026:99741 |
| Red Hat | enterprise_linux:9::appstream | rapidjson, rapidjson-doc, rapidjson-devel | 0:1.1.0-20.module+el9.9.0+25300+c0fc77bc | RHSA-2026:99741 |
| Rocky Linux | 9 | mecab | 0:0.996-3.module+el9.8.0+40162+a76274f1.4 | RLSA-2026:99741 |
| Rocky Linux | 9 | mecab | 0:0.996-3.module+el9.8.0+40205+77f4da59.4 | RLSA-2026:99741 |
| Rocky Linux | 9 | mecab-ipadic | 0:2.7.0.20070801-24.module+el9.8.0+40162+a76274f1 | RLSA-2026:99741 |
| Rocky Linux | 9 | mecab-ipadic | 0:2.7.0.20070801-24.module+el9.8.0+40205+77f4da59 | RLSA-2026:99741 |
| Rocky Linux | 9 | perl-DBD-MySQL | 0:4.053-3.module+el9.8.0+40162+a76274f1 | RLSA-2026:99741 |
| Rocky Linux | 9 | perl-DBD-MySQL | 0:4.053-3.module+el9.8.0+40205+77f4da59 | RLSA-2026:99741 |
| Azure Linux | 3 | opencc | no fix listed | AZL-111712 |
| Azure Linux | 3 | rapidjson | no fix listed | AZL-111134 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.
Red Hat rates this Important.
This issue is in RapidJSON's internal regular expression engine
(GenericStringStream::Take / GenericRegex), which can be reached when processing
untrusted regex input such as JSON Schema "pattern" values.
Red Hat MySQL 8.4 builds RapidJSON with RAPIDJSON_SCHEMA_USE_INTERNALREGEX=0
and RAPIDJSON_SCHEMA_USE_STDREGEX=1 (see cmake/rapidjson.cmake). So, the vulnerable code path is not reachable in the MySQL server. The bundled RapidJSON sources may still report as version 1.1.0.
Where Red Hat ships rapidjson-devel (for example via the mysql:8.4 module) the package provides headers only. There is no vulnerable executable in that package. Systems are not vulnerable solely because rapidjson-devel is installed. Applications built from those headers are only at risk if they enable RapidJSON's internal regex engine and feed it untrusted patterns.
No mitigation is required for Red Hat MySQL packages. MySQL is built with
RAPIDJSON_SCHEMA_USE_INTERNALREGEX=0 and RAPIDJSON_SCHEMA_USE_STDREGEX=1. So, the vulnerable RapidJSON internal regex parser is not used.
The rapidjson-devel package ships only C++ header files and contains no executable code. Merely installing rapidjson-devel does not expose a system to this flaw. Developers who build applications against rapidjson-devel and use JSON Schema pattern matching should compile with -DRAPIDJSON_SCHEMA_USE_INTERNALREGEX=0 -DRAPIDJSON_SCHEMA_USE_STDREGEX=1
(or equivalent) so the C++ standard library regex engine is used instead of RapidJSON's internal regex implementation.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | dotnet11.0 | Not affected | |
| Red Hat Enterprise Linux 10 | mysql8.4 | Not affected | |
| Red Hat Enterprise Linux 8 | mysql:8.4/mysql | Not affected | |
| Red Hat Enterprise Linux 9 | dotnet11.0 | Not affected | |
| Red Hat Enterprise Linux 9 | mysql:8.4/mysql | Not affected | |
| Red Hat Enterprise Linux 9 | mysql:8.4/rapidjson | Affected | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rapidjson | Affected | |
| Red Hat OpenStack Platform 17.1 | leatherman | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-116620.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).