CVE-2025-26646VulnerabilityPublished 20 Apr 2026Updated 5 Oct 2026

Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-55315

Not known to be exploited.

Data as of 26 Oct 2026, 11:07 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

Description

This update includes the following RPMs: dotnet8.0: * aspnetcore-runtime-8.0-8.0.26-1.hum1 (aarch64, x86_64) * aspnetcore-runtime-dbg-8.0-8.0.26-1.hum1 (aarch64, x86_64) * aspnetcore-targeting-pack-8.0-8.0.26-1.hum1 (aarch64, x86_64) * dotnet-apphost-pack-8.0-8.0.26-1.hum1 (aarch64, x86_64) * dotnet-hostfxr-8.0-8.0.26-1.hum1 (aarch64, x86_64) * dotnet-runtime-8.0-8.0.26-1.hum1 (aarch64, x86_64) * dotnet-runtime-dbg-8.0-8.0.26-1.hum1 (aarch64, x86_64) * dotnet-sdk-8.0-8.0.126-1.hum1 (aarch64, x86_64) * dotnet-sdk-8.0-source-built-artifacts-8.0.126-1.hum1 (aarch64, x86_64) * dotnet-sdk-dbg-8.0-8.0.126-1.hum1 (aarch64, x86_64) * dotnet-targeting-pack-8.0-8.0.26-1.hum1 (aarch64, x86_64) * dotnet-templates-8.0-8.0.126-1.hum1 (aarch64, x86_64) * dotnet8.0-8.0.126-1.hum1.src (src)

CWE-290Authentication Bypass by Spoofing (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
OWASP Cheat Sheets
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.5.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Web Services API Signature Forgery Leveraging Hash Function Extension Weakness (opens in a new tab)
Signature Spoof (opens in a new tab)
Signature Spoofing by Misrepresentation (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-377Insecure Temporary File (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
Creating and using insecure temporary files can leave application and system data vulnerable to attack.
OWASP Cheat Sheets
Authorization (opens in a new tab)
Attack patterns
Explore for Predictable Temporary File Names (opens in a new tab)
Screen Temporary Files for Sensitive Information (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-319Cleartext Transmission of Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Architecture and Design
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
Implementation
When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Implementation
When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
V1.9.1 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Harvesting Information via API Event Monitoring (opens in a new tab)
Signature Spoofing by Mixing Signed and Unsigned Content (opens in a new tab)
Sniff Application Code (opens in a new tab)
Interception (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-444Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
Implementation
Use a web server that employs a strict HTTP parsing procedure, such as Apache.
Implementation
Use only SSL communication.
Implementation
Terminate the client session after each request.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.5 (opens in a new tab)
Attack patterns
HTTP Response Smuggling (opens in a new tab)
HTTP Request Smuggling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-776Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product uses XML documents and allows their structure to be defined with a Document Type Definition (DTD), but it does not properly control the number of recursive definitions of entities.
Operation
If possible, prohibit the use of DTDs or use an XML parser that limits the expansion of recursive DTD entities.
Implementation
Before parsing XML files with associated DTDs, scan for recursive entity declarations and do not continue parsing potentially explosive content.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
Exponential Data Expansion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-138Improper Neutralization of Special Elements (opens in a new tab)
Class weaknessOWASP Top 10 A03:2021: Injection (opens in a new tab)
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as control elements or syntactic markers when they are sent to a downstream component.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Implementation
Developers should anticipate that special elements (e.g. delimiters, symbols) will be injected into input vectors of their product. One defense is to create an allowlist (e.g. a regular expression) that defines valid input according to the requirements specifications.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation
Use and specify an appropriate output encoding to ensure that the special elements are well-defined. A normal byte sequence in one encoding could be a special element in another.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V5.2.2 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
HTTP Request Splitting (opens in a new tab)
Command Delimiters (opens in a new tab)
HTTP Response Splitting (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Description

WeaknessesCWE-290, CWE-377, CWE-319 +4

Technical details

References

Community reviews

Related threats