CVE-2026-55165 Netflix CVE debrief

Who should care

Defenders responsible for Lemur deployments should assess exposure and prioritize verification and remediation efforts. They should review their token secrets and consider implementing additional security measures to prevent potential algorithm confusion attacks. Operators of affected systems should also verify their deployment and upgrade to version 1.9.2 or later.

Why it matters

A defense-in-depth gap in Lemur's JWT verifier prior to version 1.9.2 could lead to algorithm confusion and weaken anomaly detection. Defenders should verify their deployment and upgrade to version 1.9.2 or later.

• Potential algorithm confusion after asymmetric-signing migration
• Weakened algorithm-based anomaly detection
• Verification of token secrets required to prevent forged HS256 tokens

Technical summary

The Lemur JWT verifier prior to version 1.9.2 used an attacker-controlled algorithm value from an unverified token, which could lead to algorithm confusion after an asymmetric-signing migration. The fix introduces a server-controlled algorithm allowlist and defaults it to HS256. This change helps prevent potential algorithm confusion attacks by ensuring only authorized algorithms are used. The verifier's previous behavior could weaken algorithm-based anomaly detection because the token chooses the recorded value. A separate disclosure of LEMUR_TOKEN_SECRET would also permit forged HS256 tokens, although that disclosure is an independent prerequisite.

Defensive priority

Defenders should prioritize verifying their Lemur deployment against this issue and upgrading to version 1.9.2 or later. They should also review their token secrets and consider implementing additional security measures to prevent potential algorithm confusion attacks.

Recommended defensive actions

• Verify Lemur deployment against CVE-2026-55165
• Upgrade to Lemur version 1.9.2 or later
• Review token secrets and consider additional security measures
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• 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
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source references provide information about the issue and its fix. However, the corpus does not establish versions, exploitation, impact, or remediation beyond the provided information, and those points require verification from the supplied official sources.

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.