dbcve.org
TeamcenterApplication · Siemens

CVE-2026-33893

HIGH · 7.5 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 2312.0014 / 2406.0012 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been identified in Teamcenter V2312 (All versions < V2312.0014), Teamcenter V2406 (All versions < V2406.0012), Teamcenter V2412 (All versions < V2412.0009), Teamcenter V2506 (All versions < V2506.0005), Teamcenter V2512 (All versions). The affected application contains hardcoded key which is used for obfuscation stored directly into the application. This could allow an attacker to obtain these keys and misuse them to gain unauthorized access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Teamcenter contains hardcoded obfuscation keys embedded directly in the application binary/code. Attackers who obtain these keys through code analysis or decompilation can use them to decode sensitive data or gain unauthorized access to the system.

MitigationReplace all hardcoded keys with a secure key management solution (e.g., external vault, environment variables, or secure configuration) and rotate any keys that may have been exposed. Apply vendor-supplied patches for the affected versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TeamcenterApplication
Affected:>= 2312.0, < 2312.0014>= 2406.0, < 2406.0012>= 2412.0, < 2412.0009>= 2506.0, < 2506.0005

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Teamcenter version
    Access the Teamcenter Administration interface or check the version file in the installation directory (typically under the Teamcenter installation path such as %TC_ROOT%\version or via the About dialog in the application)
    Affected if The installed version falls within any of these ranges: 2312.0 to 2312.0013, 2406.0 to 2406.0011, 2412.0 to 2412.0008, or 2506.0 to 2506.0004
  2. Locate Teamcenter binary and configuration directories
    Navigate to the Teamcenter installation root directory (commonly C:\Siemens\Teamcenter or /opt/Teamcenter) and identify the main application binaries, JAR files, or configuration folders where application code resides
    Affected if Hardcoded keys would be embedded within the application binaries or configuration files shipped with the affected versions
  3. Search for obfuscation keys in application binaries
    Use a text search tool (such as strings, grep, or a hex editor) to scan Teamcenter JAR files or DLLs for suspicious patterns like base64-encoded strings, encryption key identifiers, or known obfuscation-related keywords (e.g., 'key', 'obfuscate', 'encrypt', 'secret')
    Affected if Hardcoded obfuscation keys are present in the binary code and can be extracted through static analysis or decompilation
  4. Review configuration for external key management
    Examine Teamcenter configuration files (typically in the %TC_ROOT%\config directory or similar) to determine whether sensitive operations rely on externally managed keys (environment variables, vault services) rather than hardcoded values embedded in code
    Affected if The application relies on keys embedded directly in binaries rather than external secure key management solutions

A system is affected if the installed Teamcenter version matches any of the four affected version ranges AND the application contains hardcoded obfuscation keys within its binaries or shipped configuration files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2312.0014 / 2406.0012 / 2412.0009 or later
Fixed in 2312.00142406.00122412.0009
Interim mitigation

Replace all hardcoded keys with a secure key management solution (e.g., external vault, environment variables, or secure configuration) and rotate any keys that may have been exposed. Apply vendor-supplied patches for the affected versions.

Recommended fix High confidence

Teamcenter V2312.0014, V2406.0012, V2412.0009, or V2506.0005 (depending on your release line)

  1. 1. Identify the current Teamcenter version by checking the application or system information.
  2. 2. Determine which version range your current installation falls into (V2312, V2406, V2412, or V2506).
  3. 3. Plan the upgrade to the minimum fixed version for your release line: V2312.0014, V2406.0012, V2412.0009, or V2506.0005 respectively.
  4. 4. Before upgrading, review Siemens Teamcenter upgrade documentation and release notes for your specific version path.
  5. 5. Perform a backup of the current Teamcenter system including database and configuration files.
  6. 6. Test the upgrade in a non-production environment first to verify compatibility with your customizations and integrations.
  7. 7. Apply the upgrade following Siemens standard upgrade procedures.
  8. 8. After upgrade, rotate any credentials or keys that may have been affected and review audit logs for any suspicious activity that may have occurred before the fix.
Caveat Enterprise PLM upgrades may have breaking changes; test thoroughly in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Teamcenter Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33893 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data