PYSEC-2026-603

Vulnerability from pysec - Published: 2026-05-28 19:16 - Updated: 2026-07-02 12:26
VLAI?
Details

An issue was discovered in OpenStack Keystone before 29.0.2. The Keystone federated token rescoping mechanism does not propagate the original token's expiry to the newly issued token. When a federated user rescopes a token via POST /v3/auth/tokens, the handle_scoped_token() function in the mapped authentication plugin returns response data without an expires_at value. The token provider falls back to issuing a token with a fresh default TTL. By rescoping repeatedly before each token expires, a user can maintain access indefinitely, bypassing operator-configured token lifetime policies. This is a variant of CVE-2012-3426. Only deployments using federated identity (SAML2, OpenID Connect) are affected.

Severity ?
8.1 (High)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Impacted products
Name purl
keystone pkg:pypi/keystone
Aliases
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {},
      "package": {
        "ecosystem": "PyPI",
        "name": "keystone",
        "purl": "pkg:pypi/keystone"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "14.0.0"
            },
            {
              "fixed": "27.0.2"
            },
            {
              "introduced": "28.0.0"
            },
            {
              "fixed": "28.0.2"
            },
            {
              "introduced": "29.0.0"
            },
            {
              "fixed": "29.0.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "14.0.0",
        "14.0.1",
        "14.1.0",
        "14.2.0",
        "15.0.0",
        "15.0.0.0rc1",
        "15.0.0.0rc2",
        "15.0.1",
        "16.0.0",
        "16.0.0.0rc1",
        "16.0.0.0rc2",
        "16.0.1",
        "16.0.2",
        "17.0.0",
        "17.0.0.0rc1",
        "17.0.0.0rc2",
        "17.0.1",
        "18.0.0",
        "18.0.0.0rc1",
        "18.1.0",
        "19.0.0",
        "19.0.0.0rc1",
        "19.0.0.0rc2",
        "19.0.1",
        "20.0.0",
        "20.0.0.0rc1",
        "20.0.1",
        "21.0.0",
        "21.0.0.0rc1",
        "21.0.1",
        "22.0.0",
        "22.0.0.0rc1",
        "22.0.1",
        "22.0.2",
        "23.0.0",
        "23.0.0.0rc1",
        "23.0.1",
        "23.0.2",
        "24.0.0",
        "24.0.0.0rc1",
        "24.1.0",
        "25.0.0",
        "25.0.0.0rc1",
        "26.0.0",
        "26.0.0.0rc1",
        "26.1.0",
        "26.1.1",
        "27.0.0",
        "27.0.0.0rc1",
        "27.0.1",
        "28.0.0",
        "28.0.1",
        "29.0.0",
        "29.0.1"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-44394"
  ],
  "details": "An issue was discovered in OpenStack Keystone before 29.0.2. The Keystone federated token rescoping mechanism does not propagate the original token\u0027s expiry to the newly issued token. When a federated user rescopes a token via POST /v3/auth/tokens, the handle_scoped_token() function in the mapped authentication plugin returns response data without an expires_at value. The token provider falls back to issuing a token with a fresh default TTL. By rescoping repeatedly before each token expires, a user can maintain access indefinitely, bypassing operator-configured token lifetime policies. This is a variant of CVE-2012-3426. Only deployments using federated identity (SAML2, OpenID Connect) are affected.",
  "id": "PYSEC-2026-603",
  "modified": "2026-07-02T12:26:33.242409Z",
  "published": "2026-05-28T19:16:38.223Z",
  "references": [
    {
      "type": "FIX",
      "url": "https://bugs.launchpad.net/keystone/+bug/2150379"
    },
    {
      "type": "FIX",
      "url": "https://security.openstack.org/ossa/OSSA-2026-015.html"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.



Detection rules are retrieved from Rulezet.