Skip to content

← Public intelligence

Maven package

org.apache.tomcat:tomcat-tribes

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5MavenPublished

    Apache Tomcat has an Improper Authentication vulnerability

    CVE-2026-55955 · GHSA-c5ph-rghf-fjfj

    Affected
    • Maven org.apache.tomcat:tomcat-tribes >= 11.0.0-M1, < 11.0.23; >= 10.1.0-M1, < 10.1.56; >= 9.0.13, < 9.0.119; >= 8.5.38, <= 8.5.100; >= 7.0.100, <= 7.0.109
    Fixed in
    10.1.569.0.11911.0.23· Partial vendor fix
    Issue
    Improper Authentication vulnerability in Apache Tomcat allowed a replay attack against the EncryptionInterceptor in the cluster component. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.22, from 10.1.0-M1 through 10.1.55, from 9.0.13 through 9.0.118, from 8.5.38 through 8.5.100, from 7.0.100 through 7.0.109. Users are recommended to upgrade to version 11.0.23, 10.1.56, 9.0.119, which fixes the issue.

    Recommended action: Upgrade to 11.0.23, 10.1.56 or 9.0.119 by release line; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5MavenPublished

    Apache Tomcat vulnerable to Insertion of Sensitive Information into Log File

    CVE-2026-34487 · GHSA-x4m4-345f-5h5g

    Affected
    • Maven org.apache.tomcat:tomcat-tribes >= 9.0.13, < 9.0.117; >= 10.1.0-M1, < 10.1.54; >= 11.0.0-M1, < 11.0.21
    Fixed in
    9.0.11711.0.2110.1.54· Vendor fix available
    Issue
    Insertion of Sensitive Information into Log File vulnerability in the cloud membership for clustering component of Apache Tomcat exposed the Kubernetes bearer token. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.20, from 10.1.0-M1 through 10.1.53, from 9.0.13 through 9.0.116. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fix the issue.

    Recommended action: Upgrade to 11.0.21, 10.1.54 or 9.0.117 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. High, CVSS 7.5Exploited · CISA KEVMavenPublished

    Apache Tomcat Missing Encryption of Sensitive Data vulnerability

    CVE-2026-34486 · GHSA-69r9-qgr7-g2wj

    Affected
    • Maven org.apache.tomcat:tomcat-tribes >= 11.0.20, <= 11.0.20; >= 10.1.53, <= 10.1.53; >= 9.0.116, <= 9.0.116
    Fixed in
    9.0.11711.0.2110.1.54· Vendor fix available
    Issue
    Missing Encryption of Sensitive Data vulnerability in Apache Tomcat due to the fix for CVE-2026-29146 allowing the bypass of the EncryptInterceptor. This issue affects Apache Tomcat: 11.0.20, 10.1.53, 9.0.116. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fix the issue.

    Recommended action: Upgrade to 11.0.21, 10.1.54 or 9.0.117 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.com (1)cisa.gov (2)Source checked Evidence →
  4. High, CVSS 8.7MavenPublished

    Apache Tomcat: Padding Oracle vulnerability in EncryptInterceptor

    CVE-2026-29146 · GHSA-h468-7pvh-8vr8

    Affected
    • Maven org.apache.tomcat:tomcat-tribes >= 9.0.13, < 9.0.116; >= 10.1.50, < 10.1.53; >= 11.0.0-M1, <= 11.0.18; >= 8.5.38, <= 8.5.100; >= 7.0.100, <= 7.0.109
    Fixed in
    11.0.209.0.11610.1.53· Partial vendor fix
    Issue
    Padding Oracle vulnerability in Apache Tomcat's EncryptInterceptor with default configuration. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.0.0-M1 through 10.1.52, from 9.0.13 through 9..115, from 8.5.38 through 8.5.100, from 7.0.100 through 7.0.109. Users are recommended to upgrade to version 11.0.19, 10.1.53 and 9.0.116, which fixes the issue.

    Recommended action: Upgrade to 11.0.20, 10.1.53 or 9.0.116 by release line; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →