← console
voxell vciy

CVE-2012-3460

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. No fix version is held. The CNA's first reference is the place to look: bugzilla.redhat.com
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

cumin: At installation postgresql database user created without password

weakness
postgresql database user created without password
affected
cumin
published ranges
redhat enterprise mrg 2.0
fixed in
No fix version in held sources.
assigned by
redhat
published
2019-11-21

check us bugzilla.redhat.com access.redhat.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
4 Feb 20220.00885
7 Mar 20230.00215scoring model v2023.03.01
10 Apr 20230.00218
17 Dec 20240.00306
17 Mar 20250.00363scoring model v2025.03.14
29 Mar 20250.00705
30 Mar 20250.00363
5 Apr 20250.00389
15 Jun 20260.01306scoring model v2026.06.15

9 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.01 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
No fix version is held. One published by the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2012-3460', '2026-10-30T23:59:59.999999Z', now());