CVE-2026-58233
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 · uneditedSAP Change and Transport System Attach Tool (ctsattach) allows an authenticated attacker to supply a specially crafted archive file which, when processed by the application�s library, can trigger insecure deserialization and lead to remote code execution (RCE) on the system. Successful exploitation requires a victim to process the malicious archive, enabling the attacker to execute the RCE and extract sensitive information and gain control over the system and its processes. This vulnerability has a high impact on confidentiality and integrity of the data, with a low impact on the availability of 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 confidenceSAP CTS Attach Tool (ctsattach) contains an insecure deserialization vulnerability where a specially crafted archive file supplied by an authenticated attacker is processed by the application's library, triggering unsafe deserialization that leads to remote code execution. The attacker requires valid authentication to upload the malicious archive, which when processed by the victim enables RCE and system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify SAP CTS Attach Tool is installedCheck for the presence of the ctsattach component in your SAP system by querying the SAP system landscape directory or checking installed software components via transaction SM37 or SAIS. Look for component name containing 'CTS Attach' or 'ctsattach'.Affected if The CTS Attach Tool component is installed on the system
-
Determine installed version of CTS AttachExecute transaction SAIS or use SAP SLM to view the installed version of the CTS Attach Tool component. Compare the version number against the latest available SAP security patch notes for this component.Affected if The installed version is older than the latest patched version or cannot be determined to be patched
-
Check if archive upload functionality is enabledReview the CTS Attach Tool configuration in transaction SPRO under SAP Web AS - Transport Management. Verify whether the attachment upload feature is active or if there are any disabled flags set for the upload functionality.Affected if The archive upload feature is enabled and accessible
-
Review authentication settings for CTS Attach accessExamine the user authentication configuration and authorizations assigned to users who can access the CTS Attach functionality. Check if the upload endpoint requires valid SAP authentication and review the associated S_RFC authorizations.Affected if Users with valid SAP credentials can access the upload functionality
-
Inspect network exposure of CTS Attach serviceReview the SAP ICM (Internet Communication Manager) configuration and web dispatcher settings to determine if the CTS Attach endpoint is exposed to untrusted networks or accessible via the internet.Affected if The CTS Attach service is reachable from outside the trusted network
A system is affected if the CTS Attach Tool component is installed with the upload feature enabled and the installed version lacks the security patch for this insecure deserialization vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the latest SAP security patches for the CTS Attach Tool component and review authentication/authorization controls around archive upload functionality. Consider implementing additional input validation and network segmentation to limit exposure.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58233 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58233 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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