CVE-2026-65537 Cyr to Lat reloaded – transliteration of links and file names vulnerability

Who is affected

How to fix it

CVE-2026-65537 affects Cyr to Lat reloaded – transliteration of links and file names and involves authorization failure. Successful exploitation may let a lower-privileged user view or change data outside their allowed scope. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. No confirmed fixed version is recorded for CVE-2026-65537; follow the linked vendor advisory, apply its mitigation, and update Cyr to Lat reloaded – transliteration of links and file names as soon as a supported patched release is available.

1. Inventory every deployment, device, package, plugin, container, build, and environment that uses Cyr to Lat reloaded – transliteration of links and file names.
2. Compare the installed version with the recorded affected range: <= 1.3.3.
3. No confirmed fixed version is recorded for CVE-2026-65537; follow the linked vendor advisory, apply its mitigation, and update Cyr to Lat reloaded – transliteration of links and file names as soon as a supported patched release is available.
4. Until patched, restrict the affected API or workflow to trusted administrators and enforce an additional access-control layer at the proxy or network boundary.
5. Review configuration, roles, tokens, network paths, and exposed endpoints connected to Cyr to Lat reloaded – transliteration of links and file names; remove access that is not required.
6. Review authentication, API, audit, and object-change logs for cross-user access, bypassed checks, or unexpected privileged actions.
7. If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.

Verify the fix

• Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-65537 in place.
• Use a safe regression test to confirm the affected authorization failure path no longer produces the vulnerable behavior.
• Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
• Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
• Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.

Related categories

Related security risks

More published guidance from the same primary category.

Trusted references

FAQ