Skip to content
Cryptography

CVE-2026-33893

8.7
High
EPSS 0.29%Patch availableMay 12, 2026

Hardcoded obfuscation key in Teamcenter enables unauthorized access.

common questions

Is CVE-2026-33893 being exploited?

Not confirmed. CVE-2026-33893 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-33893?

CVE-2026-33893 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-33893?

Yes. A fix has been recorded for CVE-2026-33893. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-33893 affect?

CVE-2026-33893 affects Teamcenter V2312 (< V2312.0014), Teamcenter V2406 (< V2406.0012), Teamcenter V2412 (< V2412.0009), Teamcenter V2506 (< V2506.0005), and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-33893?

Apply vendor patch to affected Teamcenter versions

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Teamcenter V2312 (< V2312.0014)Teamcenter V2406 (< V2406.0012)Teamcenter V2412 (< V2412.0009)Teamcenter V2506 (< V2506.0005)Teamcenter V2512 (< V2512)
impact

Attacker retrieves hardcoded key to bypass obfuscation, gaining unauthorized access to Teamcenter data and admin functions.

action required

Patch when possible

affected versions
Siemens Teamcenter V2312
  • affected< V2312.0014
Siemens Teamcenter V2406
  • affected< V2406.0012
Siemens Teamcenter V2412
  • affected< V2412.0009
Siemens Teamcenter V2506
  • affected< V2506.0005

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free