What is CVE-2025-7639?

CVE-2025-7639 is AVEVA Enterprise SCADA Deserialization of Untrusted Data. The supplied enrichment data classifies it as Deserialization mapped to CWE-502 Deserialization of Untrusted Data.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2025-7639. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2025-7639 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2025-7639 using CVSS 10, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

criticalDeserializationpublic exploit

CVE-2025-7639

CVE-2025-7639 — AVEVA Enterprise SCADA Deserialization of Untrusted Data

The vulnerability, if exploited, could allow an authenticated miscreant with "DNA Authority - Operator" privilege to tamper with serialized data, potentially resulting in code execution during deserialization under the privilege of Enterprise SCADA security group "DNA Apps".

Published Aug 14, 2026Updated Aug 14, 2026Sources: NVD, AVEVA (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

AVEVA

25 products listed

CVSS base

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Security Updates Contact your AVEVA Technical Support representative, Customer Success Manager, Account Manager, or Solution Integrator to obtain the security update best applicable to the product version currently deployed in your environment: Servers: • AVEVA Enterprise SCADA v2025 P1 or higher • AVEVA Enterprise SCADA v2024 SP1 P2 • AVEVA Enterprise SCADA v2023 SP1 P1 • AVEVA Enterprise SCADA v2022 SP2 P3 • AVEVA Enterprise SCADA v2021 SP2 P6 • AVEVA Pipeline Operations for Gas/Liquids v2025 P1 or higher • AVEVA Pipeline Operations for Gas/Liquids v2024 SP1 P2 • AVEVA Pipeline Operations f…

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
AVEVA	AVEVA Enterprise SCADA	2025	Vulnerable
AVEVA	AVEVA Enterprise SCADA	2024 to <= 2024 SP1 P01	Vulnerable
AVEVA	AVEVA Enterprise SCADA	2023 to <= 2023 SP1	Vulnerable
AVEVA	AVEVA Enterprise SCADA	2022 to <= 2022 SP2 P2	Vulnerable
AVEVA	AVEVA Enterprise SCADA	0 to <= 2021 SP2 P5	Vulnerable
AVEVA	AVEVA Enterprise SCADA	2025 P1	Patched
AVEVA	AVEVA Enterprise SCADA	2024 SP1 P2	Patched
AVEVA	AVEVA Enterprise SCADA	2023 SP1 P1	Patched
AVEVA	AVEVA Enterprise SCADA	2022 SP2 P3	Patched
AVEVA	AVEVA Enterprise SCADA	2021 SP2 P6	Patched
AVEVA	AVEVA Enterprise SCADA HMI	2024	Vulnerable
AVEVA	AVEVA Enterprise SCADA HMI	0 to <= 2023_P1	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Scope

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
10	CVSS 4.0	critical	—	—	AVEVA (CNA)

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-502 · Deserialization of Untrusted Data

Modify Application Data
Unexpected State
DoS: Resource Consumption (CPU)
Varies by Context

Mitigation: If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.

Weakness & attack patterns

CWE-502Deserialization of Untrusted Data

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-586 · Object Injection

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

🛠️ AVEVA’s SCADA fix isn’t a “click update, move on” patch: CVE-2025-7639 requires a JSON migration to close a privileged path from data tampering to code execution. https://t.co/TH57jXvw7R #JsonSerialization #ScadaSecurity #AvevaEnterpriseScada #Cve20257639 https://t.co/cNc2WMFoLS
@windowsforum· Aug 13, 2026

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable AVEVA Enterprise SCADA, AVEVA Enterprise SCADA HMI, AVEVA Pipeline Operations for Gas/Liquids, AVEVA Pipeline Integrity Monitor (delivered on Pipeline Simulation media), AVEVA Pipeline Training Simulator (delivered on Pipeline Simulation media), Measurement Advisor.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 10.0 (AV:N)
Aug 14, 2026 · NVD
Initial · CVE published
Aug 14, 2026 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

3×ModifiedAug 14, 2026 · SOCRadar CTI
1×Tweets · 1 time tweeted.Aug 14, 2026 · SOCRadar CTI

References

3 on the record

github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-225-01.json
Exploit, Third Party Advisory, NIST
www.aveva.com/content/dam/aveva/documents/support/cyber-security-updates/SecurityBulletin_AVEVA-2026-005.pdf
Vendor Advisory, NIST
www.cisa.gov/news-events/ics-advisories/icsa-26-225-01
US Government Resource, NIST

Elsewhere on this site

AVEVAevery CVE for this vendor
Deserializationsame class
CWE-502other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2025-7639 is AVEVA Enterprise SCADA Deserialization of Untrusted Data, a critical vulnerability affecting AVEVA Enterprise SCADA, AVEVA Enterprise SCADA HMI, AVEVA Pipeline Operations for Gas/Liquids, AVEVA Pipeline Integrity Monitor (delivered on Pipeline Simulation media), AVEVA Pipeline Training Simulator (delivered on Pipeline Simulation media), Measurement Advisor from AVEVA. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2025-7639. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 10 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.