CVE-2026-112075 unslothai CVE debrief

Who should care

Defenders of systems using unslothai unsloth up to 0.1.501-beta should assess exposure and prioritize upgrading to 0.1.902-beta. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure, apply mitigations, and monitor for potential impacts. The vulnerability's remote attack potential and public exploit availability heighten the urgency for affected defenders to take action.

Why it matters

The weakness in unslothai unsloth allows for use of externally-controlled input to select classes or code, which may be initiated remotely. Defenders should prioritize verifying exposure and upgrading to 0.1.902-beta.

• Verify exposure in systems using unslothai unsloth up to 0.1.501-beta
• Upgrade to version 0.1.902-beta to mitigate the weakness
• Monitor for potential remote attacks

Technical summary

The weakness in unslothai unsloth up to 0.1.501-beta affects the function FastSentenceTransformer._is_transformer_module_ref in unsloth/models/sentence_transformer.py, enabling use of externally-controlled input to select classes or code. This could allow for remote attacks. Upgrading to version 0.1.902-beta is recommended to mitigate this issue. The vulnerability has been made public and could be used for attacks, emphasizing the need for defenders to assess exposure and prioritize mitigation efforts promptly. The affected component should be upgraded.

Defensive priority

Defenders should prioritize verifying exposure in systems using unslothai unsloth up to 0.1.501-beta and upgrading to 0.1.902-beta.

Recommended defensive actions

• Verify exposure in systems using unslothai unsloth up to 0.1.501-beta
• Upgrade to version 0.1.902-beta
• Monitor for potential remote attacks
• 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 unslothai unsloth up to 0.1.501-beta. The exploit has been made available to the public. Defenders should verify exposure in systems using unslothai unsloth up to 0.1.501-beta and consider upgrading to version 0.1.902-beta as a mitigation. Additional details can be found in the official CVE Program record and NIST NVD detail page.

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.