CVE-2026-107225 qax-os CVE debrief

Who should care

Defenders who use the Excelize library in their applications should be aware of this vulnerability and take steps to verify the version of the library used and update to a fixed version as soon as it becomes available.

Why it matters

CVE-2026-107225 is a vulnerability in the Excelize library that could be used to launch a denial-of-service attack against applications using the library. Defenders should verify the version of the library used in their applications and update to a fixed version as soon as it becomes available.

• An attacker could craft a malicious styles.xml file to cause the application to panic while reading cell styling.
• The vulnerability could be used to launch a denial-of-service attack against applications using the Excelize library.
• Defenders should verify the version of the Excelize library used in their applications and update to a fixed version as soon as it becomes available.

Technical summary

The Excelize library, used for reading and writing Microsoft Excel spreadsheets in Go, is vulnerable to a panic attack. This occurs when the GetStyle function is called with a crafted styles.xml file containing negative fillId, borderId, or fontId values. The vulnerability affects versions 2.8.0 to 2.11.0 of the library. An attacker could exploit this by providing a malicious styles.xml file, causing the application to panic while reading cell styling. Defenders should prioritize verifying the version of the Excelize library used in their applications and updating to a fixed version as soon as it becomes available.

Defensive priority

Defenders should prioritize verifying the version of the Excelize library used in their applications and updating to a fixed version as soon as it becomes available.

Recommended defensive actions

• Verify the version of the Excelize library used in your application
• Update to a fixed version as soon as it becomes available
• Review and validate the styles.xml file for negative fillId, borderId, or fontId values
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability is caused by the GetStyle function's failure to check for negative fillId, borderId, or fontId values in the styles.xml file. This allows an attacker to panic the application while reading cell styling.

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.