Authenticated code execution via improper bounds checking
Published Jul 23, 2025 · Updated Feb 26, 2026
A stack-based buffer overflow in IBM Engineering Systems Design Rhapsody 9.0.2, 10.0, and 10.0.1 allows local users to execute arbitrary code. IBM identifies improper bounds checking but does not disclose the affected component, input format, or operation that copies attacker-controlled data into the stack buffer. Exploitation requires low-privileged access and can compromise application data and availability under the affected account.
Summary
What happened
A stack-based buffer overflow in IBM Engineering Systems Design Rhapsody 9.0.2, 10.0, and 10.0.1 allows local users to execute arbitrary code. IBM identifies improper bounds checking but does not disclose the affected component, input format, or operation that copies attacker-controlled data into the stack buffer. Exploitation requires low-privileged access and can compromise application data and availability under the affected account.
The record
- CVE
- CVE-2025-33076
- Published
- Jul 23, 2025
- Updated
- Feb 26, 2026
- Vendor
- IBM
- Product
- IBM Engineering Systems Design Rhapsody
- Classifications
- CWE-119
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0
- Affected versionversion=10.0.1
- Affected versionversion=9.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo