Engineering Systems Design RhapsodyApplication · Ibm

CVE-2025-33076

HIGH · 8.8 CVSS v3.1 Published 2025-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
IBM Engineering Systems Design Rhapsody 9.0.2, 10.0, and 10.0.1 is vulnerable to a stack-based buffer overflow, caused by improper bounds checking. A local user could overflow the buffer and execute arbitrary code on the system.

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

IBM Engineering Systems Design Rhapsody versions 9.0.2, 10.0, and 10.0.1 contains a stack-based buffer overflow vulnerability caused by improper bounds checking. A local authenticated user can exploit this flaw to overflow a stack buffer and execute arbitrary code with the privileges of the running process.

MitigationApply the vendor-supplied patch when available. Until then, restrict local access to trusted users only and monitor for suspicious activity targeting the Rhapsody application.

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
Engineering Systems Design RhapsodyApplication
Affected:= 9.0.2= 10.0= 10.0.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify IBM Rhapsody installation
    Check installed programs or look for Rhapsody installation directory. On Windows, check Program Files for IBM/Rhapsody folder or use Add/Remove Programs. On Linux, check /opt/IBM/Rhapsody or similar paths.
    Affected if IBM Engineering Systems Design Rhapsody is installed on the system
  2. Determine installed Rhapsody version
    Open Rhapsody and navigate to Help > About IBM Engineering Systems Design Rhapsody, or check the version information in the installation directory.
    Affected if The displayed version matches exactly 9.0.2, 10.0, or 10.0.1
  3. Compare version against affected ranges
    Match the installed version string exactly against the affected versions: 9.0.2, 10.0, and 10.0.1. Note that intermediate versions like 9.0.3 or 10.0.2 are not listed as affected.
    Affected if The installed version is exactly 9.0.2, 10.0, or 10.0.1
  4. Assess local access controls
    Review local user accounts and permissions on the system where Rhapsody is installed. Check if untrusted or non-administrative users have login access.
    Affected if Untrusted users have local account access to the system running Rhapsody

The environment is affected if IBM Engineering Systems Design Rhapsody is installed and the exact version is 9.0.2, 10.0, or 10.0.1, especially when untrusted local users have system access.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch when available. Until then, restrict local access to trusted users only and monitor for suspicious activity targeting the Rhapsody application.

Recommended fix Moderate confidence

10.0.2 or later (check IBM Fix Central for exact version)

  1. 1. Check IBM Fix Central (https://www.ibm.com/support/fixcentral/) for CVE-2025-33076 security patches
  2. 2. Download and apply the appropriate IBM Engineering Systems Design Rhapsody patch for your version
  3. 3. Verify the patch installation by checking the product version number
  4. 4. Restart the Rhapsody application if required by the patch
Caveat Review IBM release notes for potential compatibility issues with existing models or integrations

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

Fix this in Engineering Systems Design Rhapsody Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2025-33076 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