CVE-2026-50229VulnerabilityPublished 29 Jun 2026Updated 7 Nov 2026

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

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2026-55955

Authoritative record:CVE-2026-50229· Medium 6.1

Exposed hosts seen by OffSeq Mirage · public detection template (Nuclei) · CVSS 6.1 Medium : upgrade Red Hat tomcat to 8.5.101 or 7.0.110 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 4.0% chance of exploitation in 30 days – higher than 90% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.5.101, 7.0.110

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jun 2026
Detectable: evidence found.
nuclei template: Apache Tomcat - Cross-Site Scripting
Weaponized: 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: evidence found.
3 exposed hosts found; no attack traffic recorded

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), OffSeq Mirage (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

What to do

Upgrade org.apache.tomcat/tomcat to 8.5.101 or 7.0.110.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Tomcat	Affected >=11.0.0-M1 <=11.0.22 >=10.1.0-M1 <=10.1.55 >=9.0.0.M1 <=9.0.118 >=8.5.0 <=8.5.100 >=7.0.0 <=7.0.109	Fixed in–
Mavenorg.apache.tomcat/tomcat`pkg:maven/org.apache.tomcat/tomcat`Other threats	Affected =8.5.0 >=8.5.0 <8.5.101 =7.0.0 >=7.0.0 <7.0.110	Fixed in 8.5.101 7.0.110

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat advises that only Tomcat deployments configured with the EncryptionInterceptor for Tribes cluster communication are affected. Mitigation includes ensuring cluster communication channels are restricted to trusted, isolated networks. The advisory does not explicitly confirm that a patch is available for these vulnerabilities; it provides updated RPMs as bug fixes and enhancements. Users should monitor Red Hat's official errata and update to the latest RPM versions when available. If not using the EncryptionInterceptor or clustering, no action is required for this specific vulnerability.

Description

This update includes the following RPMs: tomcat11: * tomcat11-11.0.23-0.1.hum1 (noarch) * tomcat11-admin-webapps-11.0.23-0.1.hum1 (noarch) * tomcat11-common-11.0.23-0.1.hum1 (noarch) * tomcat11-docs-webapp-11.0.23-0.1.hum1 (noarch) * tomcat11-el-6.0-api-11.0.23-0.1.hum1 (noarch) * tomcat11-jsp-4.0-api-11.0.23-0.1.hum1 (noarch) * tomcat11-lib-11.0.23-0.1.hum1 (noarch) * tomcat11-servlet-6.1-api-11.0.23-0.1.hum1 (noarch) * tomcat11-user-instance-11.0.23-0.1.hum1 (noarch) * tomcat11-webapps-11.0.23-0.1.hum1 (noarch) * tomcat11-11.0.23-0.1.hum1.src (src)

Impact

The primary impact is unauthorized access or manipulation of data within the Tomcat cluster component via replay attacks on encrypted cluster messages. This affects only deployments using the EncryptionInterceptor for Tribes cluster communication, which is a non-default configuration. The vulnerability does not affect default Tomcat deployments without clustering or without the EncryptionInterceptor enabled. Red Hat downgraded the severity from important to moderate due to the requirement of adjacent network access and high attack complexity. Other listed CVEs in the advisory may have additional impacts but are not detailed here.

Summary

The advisory covers a set of vulnerabilities affecting Red Hat Hardened Images RPMs, including Apache Tomcat 11.0.23-0.1.hum1 packages. One detailed vulnerability (CVE-2026-55955) involves an improper authentication flaw in the EncryptionInterceptor component used for Tribes cluster communication in Apache Tomcat. This flaw allows a remote attacker with access to the cluster network to perform replay attacks against encrypted cluster messages. Exploitation requires the EncryptionInterceptor to be enabled, which is not the default configuration. Red Hat rates this vulnerability as moderate severity with a CVSS 3.1 vector of AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N (score 4.2). The advisory lists multiple CVEs but does not provide explicit patch availability details. The update includes new RPM versions of tomcat11 packages as bug fixes and enhancements.

CWE-79Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
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.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-358Improperly Implemented Security Check for Standard (opens in a new tab)
Base weakness
The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.
CWE-390Detection of Error Condition Without Action (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product detects a specific error, but takes no actions to handle the error.
Implementation
Properly handle each exception. This is the recommended solution. Ensure that all exceptions are handled in such a way that you can be sure of the state of your system at any given moment.
Implementation
If a function returns an error, it is important to either fix the problem and try again, alert the user that an error has happened and let the program continue, or alert the user and close and cleanup the program.
Testing
Subject the product to extensive testing to discover some of the possible instances of where/how errors or return values are not handled. Consider testing techniques such as ad hoc, equivalence partitioning, robustness and fault tolerance, mutation, and fuzzing.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-778Insufficient Logging (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.
Architecture and Design
Use a centralized logging mechanism that supports multiple levels of detail.
Implementation
Ensure that all security-related successes and failures can be logged. When storing data in the cloud (e.g., AWS S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to enable and capture detailed logging information.
Operation
Be sure to set the level of logging appropriately in a production environment. Sufficient data should be logged to enable system administrators to detect attacks, diagnose errors, and recover from attacks.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.3 (opens in a new tab)
V7.2.1 (opens in a new tab)
V7.1.4 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-294Authentication Bypass by Capture-replay (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).
Architecture and Design
Utilize some sequence or time stamping functionality along with a checksum which takes this into account in order to ensure that messages can be parsed only once.
Architecture and Design
Since any attacker who can listen to traffic can see sequence numbers, it is necessary to sign messages with some kind of cryptography to ensure that sequence numbers are not simply doctored along with content.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Kerberoasting (opens in a new tab)
Remote Services with Stolen Credentials (opens in a new tab)
Windows Admin Shares with Stolen Credentials (opens in a new tab)
Reusing Session IDs (aka Session Replay) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-551Incorrect Behavior Order: Authorization Before Parsing and Canonicalization (opens in a new tab)
Base weakness
If a web server does not fully parse requested URLs before it examines them for authorization, it may be possible for an attacker to bypass authorization protection.
Architecture and Design
URL Inputs should be decoded and canonicalized to the application's current internal representation before being validated and processed for authorization. Make sure that your application does not decode the same input twice.
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-305Authentication Bypass by Primary Weakness (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

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

Mentioned vulnerabilities

Exploitation evidence

What to do

Affected software

Description

Impact

Summary

Nuclei detection templates

Proofs of concept on GitHub

References

Community reviews

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Aug 2026, 17:58 UTC

Public exploits and detectiona Nuclei detection template, GitHub proofs of concept

WeaknessesCWE-79, CWE-358, CWE-390 +4

Technical details

References

Community reviews

Related threats