CVE-2026-97791 (GCVE-0-2026-97791)

Vulnerability from cvelistv5 – Published: 2026-10-09 10:19 – Updated: 2026-10-09 11:08
VLAI
Title
Apache CXF: STSTokenValidator can accept untrusted SAML assertions because it shares validation state between requests
Summary
In Apache CXF, STSTokenValidator checks whether a SAML assertion is signed by a trusted certificate before deciding to send it to the STS. That result was stored in one object shared by all requests, so one request could read another's result. A remote, unauthenticated attacker could send a forged assertion signed with an untrusted certificate while legitimate requests were being processed, and it could be accepted as trusted without ever reaching the STS. Only services that use STSTokenValidator to validate SAML tokens without alwaysValidateToSts set are affected.  Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
Severity
No CVSS data available.
Assigner
apache CNA under the mitre root
CNA scorecard B 76/100 over 939 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Apache Software Foundation Apache CXF Affected: 4.2.0 , < 4.2.4 (semver)
Affected: 4.0.0 , < 4.1.9 (semver)
Affected: 0 , < 3.6.13 (semver)
guessed Create a notification for this product.
Credits
MopMonk-AI
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2026-10-09T11:08:04.093Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "http://www.openwall.com/lists/oss-security/2026/10/09/10"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://repo.maven.apache.org/maven2",
          "defaultStatus": "unaffected",
          "packageName": "org.apache.cxf:cxf-rt-ws-security",
          "packageURL": "pkg:maven/org.apache.cxf/cxf-rt-ws-security",
          "product": "Apache CXF",
          "vendor": "Apache Software Foundation",
          "versions": [
            {
              "lessThan": "4.2.4",
              "status": "affected",
              "version": "4.2.0",
              "versionType": "semver"
            },
            {
              "lessThan": "4.1.9",
              "status": "affected",
              "version": "4.0.0",
              "versionType": "semver"
            },
            {
              "lessThan": "3.6.13",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "MopMonk-AI"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "In Apache CXF, \u003ccode\u003eSTSTokenValidator\u003c/code\u003e checks whether a SAML assertion is signed by a trusted certificate before deciding to send it to the STS. That result was stored in one object shared by all requests, so one request could read another\u0027s result. A remote, unauthenticated attacker could send a forged assertion signed with an untrusted certificate while legitimate requests were being processed, and it could be accepted as trusted without ever reaching the STS. Only services that use \u003ccode\u003eSTSTokenValidator\u003c/code\u003e to validate SAML tokens without \u003ccode\u003ealwaysValidateToSts\u003c/code\u003e set are affected.\u0026nbsp;\u003cbr\u003eUsers are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue."
            }
          ],
          "value": "In Apache CXF, STSTokenValidator checks whether a SAML assertion is signed by a trusted certificate before deciding to send it to the STS. That result was stored in one object shared by all requests, so one request could read another\u0027s result. A remote, unauthenticated attacker could send a forged assertion signed with an untrusted certificate while legitimate requests were being processed, and it could be accepted as trusted without ever reaching the STS. Only services that use STSTokenValidator to validate SAML tokens without alwaysValidateToSts set are affected.\u00a0\nUsers are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue."
        }
      ],
      "metrics": [
        {
          "other": {
            "content": {
              "text": "important"
            },
            "type": "Textual description of severity"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-09T10:19:26.153Z",
        "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
        "shortName": "apache"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://lists.apache.org/thread.html/ssdr417qgms9fjl0m8802xd8170wnk1l"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "Apache CXF: STSTokenValidator can accept untrusted SAML assertions because it shares validation state between requests",
      "x_generator": {
        "engine": "Vulnogram 1.0.3"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
    "assignerShortName": "apache",
    "cveId": "CVE-2026-97791",
    "datePublished": "2026-10-09T10:19:26.153Z",
    "dateReserved": "2026-09-25T04:38:00.142Z",
    "dateUpdated": "2026-10-09T11:08:04.093Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-97791",
      "date": "2026-10-10",
      "epss": "0.00168",
      "percentile": "0.05599"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "collectionURL": "https://repo.maven.apache.org/maven2",
                "defaultStatus": "unaffected",
                "packageName": "org.apache.cxf:cxf-rt-ws-security",
                "packageURL": "pkg:maven/org.apache.cxf/cxf-rt-ws-security",
                "product": "Apache CXF",
                "vendor": "Apache Software Foundation",
                "versions": [
                  {
                    "lessThan": "4.2.4",
                    "status": "affected",
                    "version": "4.2.0",
                    "versionType": "semver"
                  },
                  {
                    "lessThan": "4.1.9",
                    "status": "affected",
                    "version": "4.0.0",
                    "versionType": "semver"
                  },
                  {
                    "lessThan": "3.6.13",
                    "status": "affected",
                    "version": "0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "security@apache.org"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In Apache CXF, STSTokenValidator checks whether a SAML assertion is signed by a trusted certificate before deciding to send it to the STS. That result was stored in one object shared by all requests, so one request could read another\u0027s result. A remote, unauthenticated attacker could send a forged assertion signed with an untrusted certificate while legitimate requests were being processed, and it could be accepted as trusted without ever reaching the STS. Only services that use STSTokenValidator to validate SAML tokens without alwaysValidateToSts set are affected.\u00a0\nUsers are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue."
          }
        ],
        "id": "CVE-2026-97791",
        "lastModified": "2026-10-09T16:33:39.007",
        "metrics": {},
        "published": "2026-10-09T11:17:03.380",
        "references": [
          {
            "source": "security@apache.org",
            "url": "https://lists.apache.org/thread.html/ssdr417qgms9fjl0m8802xd8170wnk1l"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "url": "http://www.openwall.com/lists/oss-security/2026/10/09/10"
          }
        ],
        "sourceIdentifier": "security@apache.org",
        "vulnStatus": "Undergoing Analysis"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Important",
      "current_release_date": "2026-10-09T23:08:50+00:00",
      "cve": "CVE-2026-97791",
      "id": "CVE-2026-97791",
      "initial_release_date": "2026-10-09T10:19:26.153000+00:00",
      "product_status:known_affected": "10",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "org.apache.cxf/cxf-rt-ws-security: Apache CXF: Authentication bypass via shared token validation state",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97791.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.