CVE-2026-116073 leon-ai CVE debrief

Who should care

Defenders responsible for systems using Leon before commit 50df142 should assess exposure and prioritize patching. This includes developers and administrators who manage Leon installations.

Why it matters

CVE-2026-116073 is a path traversal vulnerability in Leon before commit 50df142 that allows attackers to write files outside the models directory. Defenders should prioritize verifying the version of Leon in use, restricting access to the '/download model' command, and applying the patch.

• Verify the integrity of files written by the '/download model' command.
• Restrict access to the command to prevent unauthorized use.
• Monitor for suspicious activity that could indicate exploitation.
• Apply the patch from commit 50df142 to prevent exploitation.

Technical summary

The getModelFileNameFromURL() function in Leon before commit 50df142 is vulnerable to path traversal attacks. This allows attackers to write files outside the models directory by providing a crafted URL with encoded '../' sequences. Affected product deployments should be reviewed for exposure, and defenders should prioritize verifying the version of Leon in use and applying the patch from commit 50df142 if vulnerable. Additional defensive measures include restricting access to the '/download model' command and monitoring for suspicious activity.

Defensive priority

Defenders should prioritize verifying the version of Leon in use and applying the patch from commit 50df142 if vulnerable.

Recommended defensive actions

• Verify the version of Leon in use and apply the patch from commit 50df142 if vulnerable.
• Restrict access to the '/download model' command to trusted users and validate user input.
• Monitor for suspicious activity and implement compensating controls to prevent exploitation.
• 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 description and CVSS score. However, additional information from the source references may be necessary to fully understand the vulnerability and its 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.