CVE Intelligence
Medium Access control exploit reference

CVE-2012-3426 — OpenStack Keystone token expiration issues

OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by (1) creating new tokens through token chaining, (2) leveraging possession of a token for a disabled user account, or (3) leveraging possession of a token for an account with a changed password.

Published Jul 31, 2012 · Updated Oct 26, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: redhat

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 2.3% (30-day exploitation probability)+12
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
2.3%
ahead of 83% of scored CVEs · Oct 30, 2026
Affects
OpenStack
Essex and 2 more
CVSS base
4.9
Medium · 1 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — www.openwall.com (NIST National Vulnerability Database)
  • Documented patch — launchpad.net (NIST National Vulnerability Database)
  • Pip Keystone: fixed in version 8.0.0a0 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (OpenStack Essex, OpenStack Horizon, OpenStack Keystone…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
OpenStack Essex versions not specified by the source Vulnerable NIST National Vulnerability Database
OpenStack Horizon version folsom-1 Vulnerable NIST National Vulnerability Database
OpenStack Keystone version 2012.1version 2012.1.1 Vulnerable NIST National Vulnerability Database
Pip Keystone < 8.0.0a0 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Medium
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
4.9 CVSS 2.0 Medium 6.8 4.9 nvd@nist.gov via NIST National Vulnerability Database
AV:N/AC:M/Au:S/C:P/I:P/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-264 · Permissions, Privileges, and Access Controls

Other CVEs with this weakness →

EPSS over time FIRST

Oct 25, 2026 → Oct 30, 2026 · 6 reading(s) · max 2.30%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 26, 2026 · GitHub Security Advisories
  • Affected products added · pip/keystone
    Oct 26, 2026 · GitHub Security Advisories
  • Record published
    Oct 26, 2026
  • Fix documented
    Oct 26, 2026 · NIST National Vulnerability Database
  • Affected products added · openstack/essex, openstack/horizon, openstack/keystone
    Oct 26, 2026 · NIST National Vulnerability Database
  • CVSS changed · 4.9
    Oct 26, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 26, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 26, 2026 · Alertas do Telegram
  • 2012
  • CVE published
    Jul 31, 2012 · redhat

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 26, 2026 – Oct 26, 2026
  • 1× Official description updated · Oct 26, 2026 – Oct 26, 2026

References

20 on the record

Elsewhere on this site

OpenStack
every CVE for this vendor
Access control
same class
CWE-264
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-90460 Incorrect Authorization in OpenStack Keystone Sep 11, 2026
  • CVE-2026-80183 Type Confusion in OpenStack Keystone Aug 26, 2026
  • CVE-2026-80184 Incorrect Authorization in OpenStack Keystone Aug 25, 2026
  • CVE-2026-80182 Incorrect Authorization in OpenStack Keystone Aug 25, 2026
  • CVE-2026-55748 OpenStack Horizon RC file generation does not escape special characters in project names Jun 17, 2026
  • CVE-2026-44394 OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token May 28, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2012-3426 is "OpenStack Keystone token expiration issues", rated Medium. It affects Essex (OpenStack); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.9 describes technical severity. EPSS 2.30% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.