CVE-2025-12455: OpenText™ Vertica · Observable Response Discrepancy
Affects OpenText™ VerticaSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/S:N/AU:Y/R:UExploitation evidence
Disclosed: evidence found.
CVE published 13 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenText™Vertica | Affected
| Fixed in– |
Mavencom.vertica/verticapkg:maven/com.vertica/verticaOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-12455, organizations should implement the following specific measures: 1) Restrict network access to the Vertica management console using firewalls, VPNs, or network segmentation to limit exposure to trusted administrators only. 2) Enforce strong password policies combined with account lockout or throttling mechanisms to reduce the effectiveness of brute force attempts. 3) Deploy multi-factor authentication (MFA) for all management console logins to add an additional layer of security beyond passwords. 4) Monitor authentication logs closely for repeated failed login attempts and implement automated alerts to detect brute force activity early. 5) Review and standardize authentication error messages and response times to eliminate observable discrepancies that facilitate credential enumeration. 6) Regularly update and patch Vertica software once a vendor fix becomes available. 7) Consider deploying Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with rules tailored to detect and block brute force patterns targeting Vertica. 8) Educate administrators about the risks of exposing management consoles and best practices for secure access. These targeted actions go beyond generic advice by focusing on eliminating the specific attack vector (observable response discrepancies) and strengthening authentication controls.
Description
Observable response discrepancy vulnerability in OpenText™ Vertica allows Password Brute Forcing. The vulnerability could lead to Password Brute Forcing in Vertica management console application.This issue affects Vertica: from 10.0 through 10.X, from 11.0 through 11.X, from 12.0 through 12.X.