CVE-2012-3426

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a login. Limited direct impact.

Exploit odds

2.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2012-07-31 10:45 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:43 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.3% in the next 30 days (EPSS).
• Severity: 4.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2012-07-31 10:45 UTC

Last modified

2026-06-16 23:43 UTC

Exploit probability

2.3% · EPSS, next 30 days

Weakness

CWE-264

Record status

Modified

Affected

• Openstack Essex
• Openstack Horizon folsom-1
• Openstack Keystone 2012.1
• Openstack Keystone 2012.1.1

Attack profile CVSS 2.0 · 4.9

Attack vector

Network

Complexity

Medium

Authentication

Single

Confidentiality

Partial

Integrity

Partial

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2012-3426.md and follow it. Check whether this project is affected by CVE-2012-3426. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge