CVE-2026-35089
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-35089 is a high-severity Use of Weak Credentials (CWE-1391) vulnerability in Cert (inferred from references). Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-32277
- 🇵🇱 CERT-PL: cert.pl
Vulnerability Data
In Slican telephone exchanges secure key is generated in a predictable manner using properties of the telephone exchange which can be obtained without authentication. An unauthenticated attacker can deduce the secure key and obtain admin credentials. This issue was fixed…
more
in versions below: - IPx series: version 6.61.0040 - CCT-1668: version 6.56.0430 - MAC-6400: version 6.56.0430 - CXS-0424: version 6.30.0510 The issue STILL EXISTS in End-Of-Life telephone exchanges in versions 4.xx and below: - CCT-1668 (CCT1CPU) - MAC-6400 - CXS-0424 These products were discontinued in 2011 and 2012 and and will not receive updates. These products require a hardware update in order to receive a software update. The vendor recommends that users of these devices contact the their service department directly to determine the options for upgrading.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 7 hardening rules · 3 OS baselines
V6.2.2V6.3.1V6.3.2V6.4.2
Mitigating Controls (NIST 800-53 r5) AI
IA-5 directly requires management of authenticator strength, distribution, and replacement, stopping default or guessable credentials from being introduced or used.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.AA-01's credential issuance and key-management processes directly block most weak/default credential usage, yet leave hard-coded or product-design instances of CWE-1391 only partially addressed.
Password-strength policies in PR.AA-03 directly block weak authenticators, but the control leaves hard-coded/default credentials largely unaddressed.
Hardened baselines and default-setting reviews directly block default/hard-coded creds (mostly), yet leave algorithmic guessing, reuse, and non-config sources of weak credentials untouched (partial).
Training raises password-hygiene awareness and can therefore reduce some weak-credential mistakes, yet supplies no enforcement mechanism and leaves the dominant technical sources of CWE-1391 untouched.
Role-based awareness training can reduce the chance developers or admins introduce weak credentials but supplies no enforcement or verification, leaving the bulk of CWE-1391 risk untouched.
Maintenance/patching can incidentally remove known weak-default creds in updated versions (partial forward) but does nothing to ensure credentials are strong at design, deployment or config time (none reverse).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Directly requires secure generation, distribution and storage of authentication credentials, eliminating default/hard-coded weak passwords.
Restricts privileged accounts but does not explicitly address default or hard-coded credentials for those accounts.
Requires security activities throughout the SDLC that can catch weak credentials, but does not mandate their elimination.
Secure-coding rules can prohibit hard-coded passwords, yet coverage depends on specific coding standards adopted.
Security testing can discover weak credentials, but does not guarantee they are prevented by design.
Mandates secure authentication mechanisms that preclude use of weak or default credentials.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248667 OL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. prevents CWE-1391
- V-248668 OL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/password-auth file. prevents CWE-1391
- V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-1391
RHEL 7 (1 rule)
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. prevents CWE-1391
RHEL 8 (1 rule)
- V-244533 RHEL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. prevents CWE-1391