CVE-2025-61817
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 · uneditedInCopy versions 20.5, 19.5.5 and earlier are affected by a Use After Free 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 victim must open a malicious file.
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 confidenceInCopy versions 20.5, 19.5.5 and earlier contain a Use After Free vulnerability where memory is accessed after it has been freed, allowing an attacker to execute arbitrary code. Exploitation requires a victim to open a specially crafted malicious file, typically delivered via email or compromised websites.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 19.5.5>= 20.0, < 20.5.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Locate InCopy installation directoryOn Windows, check common paths like C:\Program Files\Adobe\Adobe InCopy 2024 or C:\Program Files\Adobe\Adobe InCopy 2025. On macOS, check /Applications/Adobe InCopy 2024 or /Applications/Adobe InCopy 2025.Affected if InCopy is installed on the system
-
Identify installed InCopy versionOpen InCopy, then go to Help > About InCopy, or right-click the InCopy executable, select Properties, and view the File Version field. Alternatively, check the version in the application metadata or installer records.Affected if A version number is returned from the application
-
Compare version against affected rangesCompare your installed version number to the affected ranges: versions 19.5.5 and earlier, or versions 20.0 through 20.5.0. Any version in these ranges is vulnerable.Affected if Installed version is <= 19.5.5 OR (installed version >= 20.0 AND installed version < 20.5.1)
-
Determine if file import features are in useReview recent InCopy file activity by checking for .icml, .icml, .incx, or other InCopy document file types opened recently. Check email archives or download folders for these file types.Affected if Users have opened untrusted InCopy document files from external sources
A system is affected if Adobe InCopy version 19.5.5 or earlier, or version 20.0 through 20.5.0, is installed and users may open untrusted InCopy document files.
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.
dbcve · scoped20.5.1
Update InCopy to the latest patched version provided by Adobe. Avoid opening files from untrusted sources and implement email/attachment screening to block suspicious file types.
InCopy 20.5.1 or later (for 20.x line); InCopy 19.5.6 or later (for 19.x line)
- 1. Verify the current InCopy version by launching the application and navigating to Help > About Adobe InCopy
- 2. Close any running instances of Adobe InCopy
- 3. Open Adobe Creative Cloud desktop application or navigate to the Adobe downloads page at helpx.adobe.com
- 4. Check for available updates for Adobe InCopy
- 5. Download and install the latest version. For version 20.x users, install version 20.5.1 or later. For version 19.x users, install version 19.5.6 or later if available
- 6. Restart the computer after installation completes
- 7. Verify the installed version matches the expected fixed version by checking Help > About Adobe InCopy
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61817 — 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-2025-61817 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