dbcve.org
TeamcenterApplication · Siemens

CVE-2026-33862

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 2312.0014 / 2406.0012 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 does not properly encode or filter user-supplied data. This could allow an attacker to inject malicious code that can be executed by other users when they visit the affected page.

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 · high confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in Siemens Teamcenter. The application fails to properly encode or filter user-supplied input before rendering it in web pages, allowing attackers to inject malicious JavaScript that executes in the browsers of other users who view the affected content.

MitigationApply the vendor patches: V2312.0014 or later, V2406.0012 or later, V2412.0009 or later, V2506.0005 or later, V2512.0001 or later. Until patched, implement input validation and output encoding as compensating controls.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Teamcenter installation
    Locate the Teamcenter installation directory or check the TC_ROOT environment variable to find where Teamcenter is installed
    Affected if Teamcenter software is present in the environment
  2. Determine installed Teamcenter version
    Check the version of the installed Teamcenter instance by examining version files, installation logs, or using Teamcenter version commands
    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
  3. Verify web interface is accessible
    Confirm that the Teamcenter web client or rich client web renderer is accessible and in use
    Affected if The web interface is exposed and users can access pages where user-supplied content is displayed
  4. Identify user input points in the application
    Map areas where users can submit or upload content that gets stored and rendered to other users, such as documents, metadata fields, comments, or custom attributes
    Affected if The application allows users to create or modify content that is stored and subsequently rendered in web pages without sanitization

You are affected if your installed Teamcenter version is within any of the vulnerable version ranges AND the application renders user-supplied input in web pages without proper encoding.

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

Apply the vendor patches: V2312.0014 or later, V2406.0012 or later, V2412.0009 or later, V2506.0005 or later, V2512.0001 or later. Until patched, implement input validation and output encoding as compensating controls.

Recommended fix High confidence

2312.0014, 2406.0012, 2412.0009, 2506.0005 (depending on your current major version)

  1. Contact Siemens Support or access the Siemens Industry Online Support (SIOS) portal to obtain the appropriate patch/upgrade package for your Teamcenter version
  2. For Teamcenter V2312 users: Upgrade to V2312.0014 or later
  3. For Teamcenter V2406 users: Upgrade to V2406.0012 or later
  4. For Teamcenter V2412 users: Upgrade to V2412.0009 or later
  5. For Teamcenter V2506 users: Upgrade to V2506.0005 or later
  6. After upgrading, verify that the XSS vulnerability is remediated by testing with the Siemens-provided validation procedures
  7. Review Siemens patch notes for any additional prerequisites or post-upgrade configuration requirements

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

Fix this in Teamcenter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33862 — 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-33862 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