CVE-2026-110718 TurboDocx CVE debrief

Who should care

Defenders responsible for TurboDocx html-to-docx installations should assess exposure and apply patches or mitigations. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify the vulnerability's presence and exposure in their environment. The vulnerability's potential operational impacts require immediate attention from these stakeholders to prevent unauthorized access or data leakage.

Why it matters

CVE-2026-110718 is a server-side request forgery vulnerability in TurboDocx html-to-docx that allows attackers to make the server fetch internal URLs, potentially bypassing security controls and leading to unauthorized access or data leakage.

• Potential unauthorized access to internal resources or metadata
• Possible bypass of security controls
• Need for verification of vulnerability presence and exposure
• Potential for data leakage or system compromise

Technical summary

The vulnerability is caused by a lack of proper validation in the isValidUrl() function, allowing attackers to make the server fetch internal URLs via img src attributes. This could potentially lead to unauthorized access to internal resources or metadata. The vulnerability's technical details indicate a high severity level, emphasizing the need for defenders to prioritize verifying the vulnerability in their environment and applying necessary patches or mitigations. Affected product deployments should be identified and assessed for exposure.

Defensive priority

Defenders should prioritize verifying the vulnerability in their environment, assessing exposure, and applying patches or mitigations.

Recommended defensive actions

• Verify the vulnerability in your environment
• Assess exposure and apply patches or mitigations
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems
• Check relevant monitoring, detection, and logs for exposed assets
• Track exceptions, retest remediated assets
• Plan vendor-supported updates or mitigations through normal change control

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description and affected versions. However, additional information on exploitation or impact is limited. Defenders should verify the vulnerability in their environment, assess exposure, and apply patches or mitigations. The lack of detailed information on exploitation or impact requires defenders to take a cautious approach and thoroughly review the vulnerability's presence and exposure in their environment. Limited source information is available; CVE,

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.