VulnerabilityPublished 12 May 2026

CVE-2026-33893: Siemens Teamcenter V2312 · Use of Hard-coded Credentials

Affects Siemens Teamcenter V2312Source CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2312.0014 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2312.0014, 2406.0012, 2412.0009 +1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 May 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
SiemensTeamcenter V2312	Affected <2312.0014	Fixed in 2312.0014
SiemensTeamcenter V2406	Affected <2406.0012	Fixed in 2406.0012
SiemensTeamcenter V2412	Affected <2412.0009	Fixed in 2412.0009
SiemensTeamcenter V2506	Affected <2506.0005	Fixed in 2506.0005

AI-suggested

If you cannot patch yet, organizations should consider restricting network access to affected Teamcenter instances and monitor for unusual access patterns. Avoid relying solely on obfuscation for protecting sensitive keys and credentials. Follow Siemens advisories closely for updates on patches or mitigation recommendations.

Description

CVE-2026-33893 is a high-severity vulnerability in Siemens Teamcenter versions prior to certain patch levels across multiple releases. The issue involves hardcoded cryptographic keys embedded in the application for obfuscation purposes. An attacker who obtains these keys could misuse them to gain unauthorized access. The vulnerability has a CVSS score of 7.5, reflecting its network exploitable nature and high confidentiality impact without requiring privileges or user interaction.

Impact

The vulnerability allows attackers to obtain hardcoded cryptographic keys used for obfuscation, which could lead to unauthorized access to sensitive information or functionality within affected Siemens Teamcenter installations. The confidentiality of data is at high risk, while integrity and availability are not impacted according to the CVSS vector. Exploitation does not require privileges or user interaction and can be performed remotely over the network.

Summary

This vulnerability affects Siemens Teamcenter versions before V2312.0014, V2406.0012, V2412.0009, V2506.0005, and all versions of V2512. It arises from the presence of hardcoded keys used for obfuscation stored directly within the application binaries. Such hardcoded credentials (CWE-798) can be extracted by attackers, potentially allowing unauthorized access to protected resources or data. The CVSS 3.1 vector indicates the vulnerability is remotely exploitable without authentication and results in a high confidentiality impact but no integrity or availability impact.

CWE-798Use of Hard-coded Credentials (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains hard-coded credentials, such as a password or cryptographic key.
Architecture and Design
For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320).
Architecture and Design
For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Architecture and Design
If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
OWASP Cheat Sheets
Key Management (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.4 (opens in a new tab)
V6.4.1 (opens in a new tab)
V3.5.2 (opens in a new tab)
Attack patterns
Read Sensitive Constants Within an Executable (opens in a new tab)
Try Common or Default Usernames and Passwords (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cert-portal.siemens.com/productcert/html/ssa-827383.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 May 2026, 10:58 UTC

WeaknessesCWE-798

Technical details

References

Community reviews

Related threats