Live › vulnerability › CVE-2026-111664
Go to dashboardPortmaster before 2.2.5 exposes POST /api/v1/updates/from-url to any local process without authorization. An attacker can point it at an index they control and install older Safing-signed releases that contain already-fixed vulnerabilities.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Any machine running Portmaster before 2.2.5, since the flaw sits in its local API. Exposure requires a local process running on the same host, so a machine with no untrusted local code has a smaller risk. The sources do not say which platforms or configurations are most at risk.
No product ranges from the sources yet.
2.2.5; anything earlier is affected.2.2.5 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Safing Portmaster before 2.2.5 contains a missing authorization vulnerability that 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 page as .md · .json · in your agent: get_signal("CVE-2026-111664")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.