CVE-2026-111664 safing CVE debrief

Who should care

Defenders responsible for Safing Portmaster installations should assess exposure and prioritize verification and remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review and mitigate the vulnerability.

Why it matters

Defenders should prioritize verifying and upgrading to Portmaster 2.2.5 or later, and restrict access to the /api/v1/updates/from-url endpoint to prevent potential forced downgrade attempts.

• Potential installation of older, vulnerable versions of Portmaster
• Bypass of version checks and auto-apply settings
• Forced downgrade via /api/v1/updates/from-url endpoint

Technical summary

The vulnerability allows unprivileged local processes to force updates by calling the POST /api/v1/updates/from-url endpoint registered with api.PermitAnyone. Attackers can supply an attacker-controlled index URL that bypasses version checks and auto-apply settings, installing older Safing-signed releases carrying previously fixed vulnerabilities. This issue affects Safing Portmaster before 2.2.5 and defenders should prioritize verifying and upgrading to Portmaster 2.2.5 or later, and restrict access to the /api/v1/updates/from-url endpoint.

Defensive priority

Defenders should prioritize verifying and upgrading to Portmaster 2.2.5 or later, and restrict access to the /api/v1/updates/from-url endpoint.

Recommended defensive actions

• Verify and upgrade to Portmaster 2.2.5 or later
• Restrict access to the /api/v1/updates/from-url endpoint
• Monitor for and respond to potential forced downgrade attempts
• 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 vulnerability is described in the CVE record and source item from cve_program_cvelist_v5. Additional details are provided in references from the source item, including issue-tracking, technical-description, patch, release-notes, and third-party-advisory links.

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.