CVE-2026-116620
説明
A flaw was found in rapidjson. A remote attacker can exploit an out-of-bounds read vulnerability in the regular expression (regex) parser by providing specially crafted input. This issue primarily leads to a Denial of Service (DoS) by causing the application to crash, and may also result in the disclosure of sensitive memory contents.
詳細
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.
CVSS (Common Vulnerability Scoring System) のスコアの詳細
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
以下の CSVV メトリクスおよびスコアは予備的で、再検討の対象となります。
CVSS v3 スコアの内訳
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| ベーススコア | 7.5 | N/A | 7.3 |
| 攻撃ベクトル | Network | N/A | Network |
| 攻撃の複雑さ | Low | N/A | Low |
| 必要な権限 | None | N/A | None |
| ユーザー関与レベル | None | N/A | None |
| 範囲 | Unchanged | N/A | Unchanged |
| 機密性 | None | N/A | Low |
| 完全性への影響 | None | N/A | Low |
| 可用性への影響 | High | N/A | Low |
ベクトル
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RC:C
脆弱性の原因 (CWE) の理解
Confidentiality
Technical Impact: Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality
Technical Impact: Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other
Technical Impact: Varies by Context
The read operation could produce other undefined or unexpected results.
よくある質問
Not sure what something means? Check out our Security Glossary.
エラータ通知の受信を希望しますか? こちらで登録してください。
