CVE-2026-112055 wvWare CVE debrief

Who should care

Defenders responsible for systems or applications using wvWare wv should assess exposure and prioritize remediation efforts. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify the version of wvWare wv in use, assess exposure to crafted .doc files, and plan for remediation.

Why it matters

Defenders should care about CVE-2026-112055 as it can lead to application crashes or instability, and potentially allow for data corruption or unexpected behavior. Verification of version and exposure, as well as remediation priority for vulnerable systems, are crucial.

• Potential application crashes or instability
• Possible data corruption or unexpected behavior
• Verification of version and exposure required
• Remediation priority for vulnerable systems

Technical summary

The vulnerability exists in wvGetPAPX_FKP and wvGetCHPX_FKP functions due to an unvalidated FKP run count. Attackers can supply a crafted .doc file with a large crun value to read past the 512-byte stack buffer. This can lead to application crashes or instability, and potentially allow for data corruption or unexpected behavior. Defenders should prioritize verifying the version of wvWare wv in use and assessing exposure to crafted .doc files. Remediation efforts should focus on updating to a fixed version if available.

Defensive priority

Defenders should prioritize verifying the version of wvWare wv in use and assessing exposure to crafted .doc files. Remediation efforts should focus on updating to a fixed version if available.

Recommended defensive actions

• Verify the version of wvWare wv in use
• Assess exposure to crafted .doc files
• Update to a fixed version if available
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 6.8 and severity of MEDIUM. However, the corpus lacks specific information on exploitation, victims, or business impact.

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.