What is CVE-2026-65842?

CVE-2026-65842 is a high-severity server-side request forgery (SSRF) vulnerability in @platejs/docx-io (npm), affecting versions < 53.3.2. It is fixed in 53.3.2. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

How severe is CVE-2026-65842?

CVE-2026-65842 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @platejs/docx-io are affected by CVE-2026-65842?

@platejs/docx-io (npm) versions < 53.3.2 is affected.

Is there a fix for CVE-2026-65842?

Yes. CVE-2026-65842 is fixed in 53.3.2. Upgrade to this version or later.

Is CVE-2026-65842 exploitable, and should I be worried?

Whether CVE-2026-65842 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-65842 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-65842 in @platejs/docx-io

Q: How severe is CVE-2026-65842?

CVE-2026-65842 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @platejs/docx-io are affected by CVE-2026-65842?

@platejs/docx-io (npm) versions < 53.3.2 is affected.

Q: Is there a fix for CVE-2026-65842?

Yes. CVE-2026-65842 is fixed in 53.3.2. Upgrade to this version or later.

Q: Is CVE-2026-65842 exploitable, and should I be worried?

Whether CVE-2026-65842 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-65842 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-65842?

Upgrade @platejs/docx-io to 53.3.2 or later.

Summary

Plate: SSRF with response disclosure in DOCX image embedding

@platejs/docx-io can fetch remote image URLs while converting HTML to DOCX. When an application converts attacker-controlled HTML in a server-side or privileged environment, this can cause the application environment to make unintended outbound requests and include fetched image data in the generated DOCX.

Patched versions

Upgrade to @platejs/docx-io version 53.3.2 or later.

Workarounds

If you cannot upgrade immediately, do not pass untrusted HTML with remote image URLs to DOCX export. Sanitize untrusted HTML to remove remote image references, convert trusted images to data URIs before conversion, or run conversion in an environment with restricted outbound network access.

Credits

Thanks to EQSTLab for reporting this issue.

Impact

Applications are affected when they use @platejs/docx-io to convert untrusted HTML that may contain remote image references, especially in server-side conversion workflows or environments with access to internal network resources.

Affected package:

@platejs/docx-io versions < 53.3.2

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2026-65842 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (53.3.2); upgrading removes the vulnerable code path.

Affected versions

@platejs/docx-io (< 53.3.2)

Security releases

@platejs/docx-io → 53.3.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade @platejs/docx-io to 53.3.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-65842? CVE-2026-65842 is a high-severity server-side request forgery (SSRF) vulnerability in @platejs/docx-io (npm), affecting versions < 53.3.2. It is fixed in 53.3.2. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
How severe is CVE-2026-65842? CVE-2026-65842 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @platejs/docx-io are affected by CVE-2026-65842? @platejs/docx-io (npm) versions < 53.3.2 is affected.
Is there a fix for CVE-2026-65842? Yes. CVE-2026-65842 is fixed in 53.3.2. Upgrade to this version or later.
Is CVE-2026-65842 exploitable, and should I be worried? Whether CVE-2026-65842 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-65842 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-65842? Upgrade @platejs/docx-io to 53.3.2 or later.