Vulnerability in Safing Portmaster (CVE-2026-111664)
Summary
Vulnerability in Safing Portmaster (CVE-2026-111664). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v1/updates/from-url.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-111664 has been found in Safing Portmaster.
Attackers can target a specific entry point like POST /api/v1/updates/from-url over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Safing Portmaster CVE-2026-111664" on the vendor's site.
CVE-2026-111664 (Safing Portmaster) — CWE-306 / CVSS v3 4.4
Attack vector: local / no user interaction
Attack surface: POST /api/v1/updates/from-url
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-306) exists in Safing Portmaster. Attackers reach the vulnerable code path via POST /api/v1/updates/from-url.
Check the vendor advisory for the affected versions of Safing Portmaster. Attack surface: POST /api/v1/updates/from-url.
Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v1/updates/from-url requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Safing Portmaster を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /api/v1/updates/from-url' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/updates/from-urlへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/v1/updates/from-url on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。