CVE-2026-71498
Description
A flaw was found in node-re2, a library providing RE2 regular expression bindings for Node.js. A local attacker could exploit this vulnerability by providing a specially crafted input buffer that ends with an incomplete multi-byte UTF-8 character. This could lead to an out-of-bounds read, potentially disclosing sensitive information from adjacent memory locations.
Statement
Red Hat ships node-re2 as a dependency of the Konflux mintmaker-renovate-image (Renovate-based dependency update automation used within the Konflux CI pipeline). The shipped version (1.26.0) falls within the vulnerable range (<1.26.1); a local attacker able to supply crafted input ending in an incomplete multi-byte UTF-8 character to the RE2 regex engine could trigger an out-of-bounds read, potentially disclosing adjacent memory contents.
Mitigation
Restrict who can supply regex input or replacement templates processed by the mintmaker-renovate-image tooling; upgrade the pinned node-re2 dependency to 1.26.1 or later once available.
Common Vulnerability Scoring System (CVSS) Score Details
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).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.1 | N/A | 5.1 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | Low |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Understanding the Weakness (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.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
