Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.15% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-41700High confidence
CODESYS Development System - Deserialization of Untrusted Data
CODESYS · CODESYS Development System
7.8HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs CODESYS CODESYS Development System and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
3ADR011566 · CSAF 2.0 · revision 1 · finalABB Product Security Incident Response Team (PSIRT)CVE-2025-41700
The vendor explicitly identifies these products as affected by this CVE.
- ABB Automation Builder <2.9.1
- Summary
- A vulnerability has been discovered in the print engine of Automation Builder. If an Automation Builder project file or archive file was crafted in a specific way, the Automation Builder could execute arbitrary code when a user opens these files and configures the print/printer options or prints the project or parts of it. This arbitrary code would be executed in the context of the user who was tricked into opening the project.
- Remediation
- The problem is corrected in the following product version: - Automation Builder 2.9.1 ABB recommends that customers apply the update at earliest convenience. Automation Builder 2.9.1 is available for download from the related download site.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
An unauthenticated attacker can trick a local user into executing arbitrary code by opening a deliberately manipulated CODESYS project file with a CODESYS development system. This arbitrary code is executed in the user context.
What
An unauthenticated attacker can trick a local user into executing arbitrary code by opening a deliberately manipulated CODESYS project file with a CODESYS development system. This arbitrary code is executed in the user context.
Why
Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
What
An unauthenticated attacker can trick a local user into executing arbitrary code by opening a deliberately manipulated CODESYS project file with a CODESYS development system. This arbitrary code is executed in the user context.
Why
Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Deserialization of Untrusted Data → execute code or commands in the affected security context
- Attack surface
- Local
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-502 ↗
CWE-502: Deserialization of Untrusted Data. The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- ABB Automation Builder <2.9.1
- Action
- The problem is corrected in the following product version: - Automation Builder 2.9.1 ABB recommends that customers apply the update at earliest convenience. Automation Builder 2.9.1 is available for download from the related download site.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 1 Dec 2025 · Last source change 1 Dec 2025, 13:59 UTC · CWE-502 · Deserialization of Untrusted Data
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-199974
Product sourceVendor CSAF · ABB Product Security Incident Response Team (PSIRT)
Remediation sourceVendor CSAF · ABB Product Security Incident Response Team (PSIRT)
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.ABB Product Security Incident Response Team (PSIRT) ↗
- Before
- 0.0.0 < 3.5.21.40 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 0.0.0 < 3.5.21.40 · Fixed: The problem is corrected in the following product version: - Automation Builder 2.9.1 ABB recommends that customers apply the update at earliest convenience. Automation Builder 2.9.1 is available for download from the related download site.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.ABB Product Security Incident Response Team (PSIRT) ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.