Quick answers
- Is CVE-2026-77173 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77173 being exploited in the wild.
- How severe is CVE-2026-77173?
- Medium severity, with a CVSS score of 4.3, published 27 October 2026.
- Which products and versions are affected?
- <UNKNOWN>.
- Is there a fix for CVE-2026-77173?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-77173 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-77173?
- Check whether you run <UNKNOWN>. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a confidentiality marking bypass in document handling where files in DOCX or ODT format fail to be marked as confidential when their filenames contain a hash character. This is a filename-parsing issue where special characters (specifically #) prevent proper classification of documents containing sensitive data. The flaw requires user action to create or manipulate the file, and exposes sensitive information by circumventing access control classifications.
Affected products
- <UNKNOWN>
Timeline
- 2026-10-27: disclosed