Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-21156 is a high-severity Wrap or Wraparound (CWE-191) vulnerability in Adobe Incopy. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-21156 is an Integer Underflow (Wrap or Wraparound) vulnerability, classified as CWE-191, affecting Adobe InCopy versions 20.0, 19.5.1, and earlier. The flaw resides in the software and could result in arbitrary code execution in the context of the current user.
Exploitation requires local access (AV:L) with low complexity (AC:L), no privileges (PR:N), and user interaction (UI:R), such as opening a malicious file. Successful attacks yield high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H) without scope change (S:U), earning a CVSS v3.1 base score of 7.8.
Adobe's security bulletin APSB25-10 provides details on the vulnerability and mitigation, available at https://helpx.adobe.com/security/products/incopy/apsb25-10.html. The advisory was published on 2025-02-11.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-2248
Vulnerability Data
InCopy versions 20.0, 19.5.1 and earlier are affected by an Integer Underflow (Wrap or Wraparound) vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a…
more
victim must open a malicious file.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static/dynamic analysis directly find integer underflow defects before code is released.
Security engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer underflow during subtraction.
Input validation can reject or sanitize values that would cause a subtraction to underflow the representable range.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent integer underflow defects via input validation, bounds checking, and static analysis.
Vulnerability scanning and code analysis can surface underflow flaws after they are introduced.
Routine patching can remediate known underflow bugs once they are discovered in deployed software.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches integer underflow defects before release.
Secure development lifecycle mandates input validation and arithmetic checks that prevent integer underflow.
Application security requirements include bounds checking and safe arithmetic to avoid underflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards directly prescribe safe integer handling and overflow/underflow prevention.