dbcve.org
Type ConfusionWeakness · CWE-843

CVE-2025-29867

HIGH · 8.5 CVSS v4.0 Published 2026-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
No privileges

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 · unedited
Access of Resource Using Incompatible Type ('Type Confusion') vulnerability in Hancom Inc. Hancom Office 2018, Hancom Inc. Hancom Office 2020, Hancom Inc. Hancom Office 2022, Hancom Inc. Hancom Office 2024 allows File Content Injection.This issue affects Hancom Office 2018: before 10.0.0.12681; Hancom Office 2020: before 11.0.0.8916; Hancom Office 2022: before 12.0.0.4426; Hancom Office 2024: before 13.0.0.3050.

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 confidence

A type confusion vulnerability in Hancom Office allows attackers to inject malicious content into files processed by the application. The vulnerability stems from improper type handling during file parsing, which can be exploited by crafting malicious document files that trigger the type confusion to inject arbitrary content.

MitigationUpdate Hancom Office to the patched versions: 10.0.0.12681 or later for 2018, 11.0.0.8916 or later for 2020, 12.0.0.4426 or later for 2022, and 13.0.0.3050 or later for 2024. Avoid opening untrusted document files until updates are applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Hancom Office is installed
    On Windows, open Control Panel > Programs and Features, or search for 'Hancom' in the Start menu. Look for entries such as 'Hancom Office 2018', 'Hancom Office 2020', 'Hancom Office 2022', or 'Hancom Office 2024'.
    Affected if Hancom Office is not installed on the system - not affected.
  2. Identify the installed Hancom Office version
    In Programs and Features, click on the Hancom Office entry to view the version column. Alternatively, navigate to the installation directory (typically C:\Program Files\Hancom\Hancom Office) and right-click on the main executable (such as hoffice.exe) to view Properties > Details for the File Version.
    Affected if Cannot determine the version - treat as potentially affected if the product is installed.
  3. Map version number to product line
    Hancom Office versions follow patterns: 10.x.x.xxxx = 2018, 11.x.x.xxxx = 2020, 12.x.x.xxxx = 2022, 13.x.x.xxxx = 2024. The first number indicates the product version line.
    Affected if Version does not match any of these patterns - may be a different product or unreleased version.
  4. Compare installed version against vulnerable ranges
    For each product line, check if the version is below the patched release: 2018 (10.0.0.xxxx where xxxx < 12681), 2020 (11.0.0.xxxx where xxxx < 8916), 2022 (12.0.0.xxxx where xxxx < 4426), 2024 (13.0.0.xxxx where xxxx < 3050).
    Affected if Installed version falls within the vulnerable ranges for any product line - affected.
  5. Assess the attack surface exposure
    This vulnerability is triggered when Hancom Office opens a maliciously crafted document file. Review whether users in your environment commonly open documents from untrusted or external sources, or if there are filters/controls on file imports.
    Affected if Users process untrusted document files without additional security controls - higher exposure risk.

A system is affected if Hancom Office is installed with a version below 10.0.0.12681 (2018), 11.0.0.8916 (2020), 12.0.0.4426 (2022), or 13.0.0.3050 (2024), and users open document files from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Hancom Office to the patched versions: 10.0.0.12681 or later for 2018, 11.0.0.8916 or later for 2020, 12.0.0.4426 or later for 2022, and 13.0.0.3050 or later for 2024. Avoid opening untrusted document files until updates are applied.

Recommended fix High confidence

Upgrade to Hancom Office 2018 (10.0.0.12681+), 2020 (11.0.0.8916+), 2022 (12.0.0.4426+), or 2024 (13.0.0.3050+) depending on your product line

  1. Identify the installed Hancom Office version (2018, 2020, 2022, or 2024) from the application's About or Help menu
  2. Navigate to the official Hancom website (www.hancom.com) or authorized download center
  3. Download the patched version: Hancom Office 2018 version 10.0.0.12681 or later; Hancom Office 2020 version 11.0.0.8916 or later; Hancom Office 2022 version 12.0.0.4426 or later; Hancom Office 2024 version 13.0.0.3050 or later
  4. Run the installer and follow the prompts to update the software
  5. Restart the application after installation completes
  6. Verify the installed version matches or exceeds the fixed version numbers specified above
Caveat Standard office software minor version updates typically have minimal breaking changes; review release notes for any feature modifications or file format compatibility notes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29867 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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