CVE-2021-38096
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 · uneditedCoreip.dll in Corel PDF Fusion 2.6.2.0 is affected by an Out-of-bounds Write vulnerability when parsing a crafted file. An unauthenticated attacker could leverage this vulnerability to achieve 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 PDF 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 confidenceCoreip.dll in Corel PDF Fusion 2.6.2.0 contains an out-of-bounds write vulnerability triggered when parsing a crafted malicious PDF file, allowing an unauthenticated attacker to achieve arbitrary code execution in the context of the current user.
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= 2.6.2.0CVSS 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.
-
Confirm Corel PDF Fusion is installedOpen Windows Control Panel, go to Programs and Features, or use PowerShell: Get-WmiObject -Class Win32_Product | Select-Object Name, VersionAffected if Corel PDF Fusion appears in the installed programs list
-
Identify the installed versionIn Programs and Features, find Corel PDF Fusion and note the version column, or right-click the application in the Start menu and select Properties to view version informationAffected if The installed version is exactly 2.6.2.0
-
Locate the coreip.dll fileSearch for coreip.dll in the Corel PDF Fusion installation directory. Common paths include C:\Program Files\Corel\PDF Fusion\ or C:\Program Files (x86)\Corel\PDF Fusion\Affected if coreip.dll exists in the Corel PDF Fusion installation folder and the version is 2.6.2.0
-
Determine exposure to malicious PDF filesReview whether users in the environment have the ability to open PDF files from untrusted or unknown sources using Corel PDF FusionAffected if Users can open untrusted PDF files with Corel PDF Fusion version 2.6.2.0
A user is affected if Corel PDF Fusion version 2.6.2.0 is installed and users can open PDF files with it, as the vulnerability is triggered during PDF parsing.
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 vendor-supplied patch or update Corel PDF Fusion to the latest version. Until patched, instruct users not to open untrusted PDF files from unknown sources.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-38096 — 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-2021-38096 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