CVE-2026-111237 Ultralytics CVE debrief

Who should care

Defenders responsible for systems using Ultralytics FastSAM, especially those with local access to the affected component, should assess exposure and prioritize verification. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Defenders should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

Defenders should prioritize verifying the affected component in their inventory and assessing exposure to local access vectors due to the weakness in Ultralytics FastSAM.

• Verification of affected component in inventory is required
• Assessment of exposure to local access vectors is necessary
• Monitoring for updates from the vendor is recommended

Technical summary

The weakness in Ultralytics FastSAM is located in the ultralytics/nn/autobackend.py file, specifically in the session.get_modelmeta.custom_metadata_map function. Manipulation of the imgsz/names/kpt_shape argument can cause improper neutralization of directives in dynamically evaluated code. This requires local access and is related to CWE-94 and CWE-95. The product uses a rolling release model to deliver continuous updates, making specific version information for affected or updated releases unavailable. The project was informed of the problem early through an issue report but has not responded yet.

Defensive priority

Defenders should prioritize verifying the affected component in their inventory and assessing exposure to local access vectors.

Recommended defensive actions

• Verify the affected component in your inventory
• Assess exposure to local access vectors
• Monitor for updates from the vendor
• 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 weakness in Ultralytics FastSAM, including its location in the ultralytics/nn/autobackend.py file and the required local access for exploitation. The weakness allows for improper neutralization of directives in dynamically evaluated code due to manipulation of the imgsz/names/kpt_shape argument in the session.get_modelmeta.custom_metadata_map function. Defenders should verify the affected component in their inventory and assess exposure to local access vectors. Evidence is limited to

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.