GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CVE-2026-19625 (GCVE-0-2026-19625)

Vulnerability from cvelistv5 – Published: 2026-09-08 20:18 – Updated: 2026-09-08 20:18
VLAI
Title
IBM Enterprise Build of Quarkus is affected by multiple vulnerabilities
Summary
When a Quarkus application has multiple endpoints secured by individual OIDC provider tenants, such as "/oidc-provider1" that is secured by the OIDC Provider 1 and "/oidc-provider2" that is secured by the OIDC Provider 2, and an optional token introspection cache is also enabled, then a valid token issued by the OIDC Provider 1 that can be used to access "/oidc-provider1" can also be used to access "/oidc-provider2" that is secured by another OIDC Provider 2.
CWE
  • CWE-284 - Improper Access Control
Assigner
References
URL Tags
https://www.ibm.com/support/pages/node/7286498 vendor-advisorypatch
Impacted products
Vendor Product Version CPE status
IBM Enterprise Build of Quarkus Affected: 3.27.1 , ≤ 3.27.5 (semver)
Affected: 3.33.1 , ≤ 3.33.3 (semver)
    cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.27.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.27.5:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.33.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.33.3:*:*:*:*:*:*:*
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.27.1:*:*:*:*:*:*:*",
            "cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.27.5:*:*:*:*:*:*:*",
            "cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.33.1:*:*:*:*:*:*:*",
            "cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.33.3:*:*:*:*:*:*:*"
          ],
          "product": "Enterprise Build of Quarkus",
          "vendor": "IBM",
          "versions": [
            {
              "lessThanOrEqual": "3.27.5",
              "status": "affected",
              "version": "3.27.1",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "3.33.3",
              "status": "affected",
              "version": "3.33.1",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Michael Read (https://github.com/Michael-JRead) , Michael Read (https://github.com/Michael-JRead)"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eWhen a Quarkus application has multiple endpoints secured by individual OIDC provider tenants, such as \"/oidc-provider1\" that is secured by the OIDC Provider 1 and \"/oidc-provider2\" that is secured by the OIDC Provider 2, and an optional token introspection cache is also enabled, then a valid token issued by the OIDC Provider 1 that can be used to access \"/oidc-provider1\" can also be used to access \"/oidc-provider2\" that is secured by another OIDC Provider 2.\u003c/p\u003e"
            }
          ],
          "value": "When a Quarkus application has multiple endpoints secured by individual OIDC provider tenants, such as \"/oidc-provider1\" that is secured by the OIDC Provider 1 and \"/oidc-provider2\" that is secured by the OIDC Provider 2, and an optional token introspection cache is also enabled, then a valid token issued by the OIDC Provider 1 that can be used to access \"/oidc-provider1\" can also be used to access \"/oidc-provider2\" that is secured by another OIDC Provider 2."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "NONE",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-284",
              "description": "CWE-284 Improper Access Control",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-08T20:18:52.521Z",
        "orgId": "9a959283-ebb5-44b6-b705-dcc2bbced522",
        "shortName": "ibm"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory",
            "patch"
          ],
          "url": "https://www.ibm.com/support/pages/node/7286498"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eThe issues are addressed in IBM Enterprise Build of Quarkus 3.27.5.SP1 and 3.33.3.SP1. To update your project to IBM Enterprise Build of Quarkus 3.27.5.SP1 or 3.33.3.SP1, follow the instructions in the \u003ca href=\"https://www.ibm.com/docs/en/quarkus/3.27.x?topic=overview-learn-whats-new-in-327#proc_updating-quarkus-maven\" rel=\"nofollow\"\u003eproduct documentation\u003c/a\u003e.\u003c/p\u003e"
            }
          ],
          "value": "The issues are addressed in IBM Enterprise Build of Quarkus 3.27.5.SP1 and 3.33.3.SP1. To update your project to IBM Enterprise Build of Quarkus 3.27.5.SP1 or 3.33.3.SP1, follow the instructions in the  product documentation https://www.ibm.com/docs/en/quarkus/3.27.x ."
        }
      ],
      "title": "IBM Enterprise Build of Quarkus is affected by multiple vulnerabilities"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "9a959283-ebb5-44b6-b705-dcc2bbced522",
    "assignerShortName": "ibm",
    "cveId": "CVE-2026-19625",
    "datePublished": "2026-09-08T20:18:52.521Z",
    "dateReserved": "2026-08-12T15:04:25.674Z",
    "dateUpdated": "2026-09-08T20:18:52.521Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-19625",
      "date": "2026-09-09",
      "epss": "0.00313",
      "percentile": "0.23907"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-19625\",\"sourceIdentifier\":\"psirt@us.ibm.com\",\"published\":\"2026-09-08T21:17:05.717\",\"lastModified\":\"2026-09-09T15:41:55.983\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"When a Quarkus application has multiple endpoints secured by individual OIDC provider tenants, such as \\\"/oidc-provider1\\\" that is secured by the OIDC Provider 1 and \\\"/oidc-provider2\\\" that is secured by the OIDC Provider 2, and an optional token introspection cache is also enabled, then a valid token issued by the OIDC Provider 1 that can be used to access \\\"/oidc-provider1\\\" can also be used to access \\\"/oidc-provider2\\\" that is secured by another OIDC Provider 2.\"}],\"affected\":[{\"source\":\"psirt@us.ibm.com\",\"affectedData\":[{\"vendor\":\"IBM\",\"product\":\"Enterprise Build of Quarkus\",\"cpes\":[\"cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.27.1:*:*:*:*:*:*:*\",\"cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.27.5:*:*:*:*:*:*:*\",\"cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.33.1:*:*:*:*:*:*:*\",\"cpe:2.3:a:ibm:enterprise_build_of_quarkus:3.33.3:*:*:*:*:*:*:*\"],\"versions\":[{\"version\":\"3.27.1\",\"lessThanOrEqual\":\"3.27.5\",\"versionType\":\"semver\",\"status\":\"affected\"},{\"version\":\"3.33.1\",\"lessThanOrEqual\":\"3.33.3\",\"versionType\":\"semver\",\"status\":\"affected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"psirt@us.ibm.com\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N\",\"baseScore\":5.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"LOW\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":3.9,\"impactScore\":1.4}]},\"weaknesses\":[{\"source\":\"psirt@us.ibm.com\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-284\"}]}],\"references\":[{\"url\":\"https://www.ibm.com/support/pages/node/7286498\",\"source\":\"psirt@us.ibm.com\"}]}}",
    "redhat_vex": {
      "aggregate_severity": "Important",
      "current_release_date": "2026-09-08T20:39:45+00:00",
      "cve": "CVE-2026-19625",
      "id": "CVE-2026-19625",
      "initial_release_date": "2026-08-31T11:55:20.525000+00:00",
      "product_status:known_affected": "3",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "quarkus-oidc: Quarkus OIDC: Cross-tenant authentication bypass via shared token-introspection cache",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19625.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…