CVE-2026-32990VulnerabilityPublished 8 Sep 2026Updated 22 Oct 2026

SUSE · Security update for tomcat10

Affects SUSESource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-32990· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in SUSE package updates : update SUSE tomcat when convenient.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11.0.20, 10.1.53, 9.0.116

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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: None: There is no loss of integrity within 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 9 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
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: 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 31 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.
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 11.0.20, 10.1.53 or 9.0.116.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Tomcat	Affected >=11.0.15 <=11.0.19 >=10.1.50 <=10.1.52 >=9.0.113 <=9.0.115	Fixed in–
Mavenorg.apache.tomcat/tomcat`pkg:maven/org.apache.tomcat/tomcat`Other threats	Affected >=11.0.15 <11.0.20 >=10.1.50 <10.1.53 >=9.0.113 <9.0.116	Fixed in 11.0.20 10.1.53 9.0.116

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

Description

This update for tomcat10 fixes the following issues: - CVE-2026-65182: Bypass longest prefix security constraint (bsc#1276893). - CVE-2026-65183: TOCTOU when setting specific permissions for Unix Domain Sockets (bsc#1276894). - CVE-2026-65637: HTTP/2 no-authority bypass of strict SNI validation - fix incomplete (bsc#1276895). - CVE-2026-65905: Limited replay attack possible with DIGEST authentication (bsc#1276896). - CVE-2026-65927: RewriteValve [N] restarts at the second rule and may bypass access control (bsc#1276897). - CVE-2026-66299: memory exhaustion via maliciously slow clients due to the WebSocket chat example providing an unbounded buffer for undelivered messages (bsc#1273150). - CVE-2026-66422: Servlet role references can bypass declarative role constraints (bsc#1276898). - CVE-2026-68525: Redirect after FORM auth may bypass method specific constraints (bsc#1276899). - CVE-2026-68569: Principal lookup can fail open in some cases (bsc#1276900). - CVE-2026-68763: DoS via allocation leak in HTTP/2 backlog tracking when a stream is reset (bsc#1276901). - CVE-2026-73180: Authenticated WebSocket session survives end of HTTP session (bsc#1276902). Changes for tomcat10: - Update to Tomcat 10.1.59 * Catalina + Fix: Ensure that a login-config conflict when merging web.xml fragments triggers a deployment failure. (markt) + Code: Remove unnecessary calls to String.intern() in the parsing of configuration files. (markt) + Fix: Extend sessionAttributeValueClassNameFilter to include filtering of dynamic proxy interface classes. (markt) + Fix: Attempt to use rollback when persisting user data to the DataSourceUserDatabase fails and improve error reporting. (remm) + Fix: 70143: Handle InvalidFileNameException when parsing parts to rethrow it as an IllegalStateException as mandated by the Servlet specification. (remm) + Fix: Add missing reason to the JsonErrorReportValve. (remm) + Fix: evaluation of the N and C flags for rewrite rules. (remm) + Fix: qsd flag should always discard the original query string when rewriting. (remm) + Fix: Add appropriate escaping for context path, current directory name and parent directory name for directory listings produced by the default servlet. Ensure XML escaping is used with XML output. (markt) + Fix: When processing certificate subject names and issuer names within RewriteValve rules, always use the RFC 2253 format name. (markt) + Fix: the incorrect rejection of requests using digest authentication when the client provided nonce count is at the upper boundary of the window (markt). + Update: Separate the Context role mapping from the Servlet specification security-role-ref. (remm) + Fix: Handle the case where the JNDIRealm is configured to perform role searches with userRoleAttribute but the attribute is not available or not configured for the current user. (markt) + Fix: Improve handling of session attribute addition concurrent with session expiration. An application will now either see a successful addition followed by expiration or the addition will not succeed. It is no longer possible for the session to expire and the addition to succeed. This is of particular not for attributes that implement HttpSessionBindingListener. (markt) + Fix: Add a new attribute to the Context, urlPatternsProvidedInDecodedForm. This attribute controls whether URLs and URL patterns provided in the deployment descriptor (web.xml), annotations and/or their programmatic equivalents are treated as being provided in URL-encoded form (i.e. using %nn encoding) or in decoded form. The Servlet specification requires that they are provided in decoded form. However, Tomcat has historically treated them as if they are provided in encoded form. In Tomcat 12, they will always be treated as if they are provided in decoded form. This setting enables migration from encoded form to decoded form on an application by application basis. This attribute will be removed in Tomcat 12 where it will effectively be hard-coded to true. (markt) + Fix: Ensure the security constraint with the longest matching path is selected when more than one constraint matches the request path. (markt) + Fix: If the request saved by FORM authentication uses a method other than GET, ensure that the security constraints are re-assessed after the saved request is restored and before it is processed. Custom Authenticator implementations that extend FormAuthenticator and override doAuthenticate() and/or restoreRequest() will require modification. (markt) + Fix: Various improvements to the DataSourceRealm. A failure to connect to the database or an exception during either user or role lookup will now result in an authentication failure rather than a partially populated Principal. For CLIENT-CERT and SPNEGO authentication, the user must exist in the database for authentication to succeed. (markt) + Fix: Improve the handling of AsyncContext.dispatch() when the Context attribute dis

References

Community reviews

Loading reviews…