Vulnerability in BMC Helix Network Management on-prem (CVE-2026-111283)
Summary
Vulnerability in BMC Helix Network Management on-prem (CVE-2026-111283). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
BMC Helix Network Management on-prem before 26.3.01 contains an authentication bypass vulnerability that allows unauthenticated attackers to log in as the local administrator with any password when SAML single sign-on is configured. Attackers can submit the administrator username with an arbitrary password on the web login page to obtain a SuperAdmin session, modify device credentials, run device commands, and alter audit records.
Source: GitHub Security Advisories (Global) 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-111283 has been found in BMC Helix Network Management on-prem.
Successful exploitation can lead to full system takeover. CVSS score: 9.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "BMC Helix Network Management on-prem CVE-2026-111283" on the vendor's site.
CVE-2026-111283 (BMC Helix Network Management on-prem) — CWE-305 / CVSS v3 9.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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-305) exists in BMC Helix Network Management on-prem.
Check the vendor advisory for the affected versions of BMC Helix Network Management on-prem.
Severity: Critical (CVSS 9.0/10). Successful exploitation can lead to full system takeover.
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 request patterns matching this CVE's known IOCs. 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・依存マニフェストで BMC Helix Network Management on-prem を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web docs.helixops.ai
- web disclosure@vulncheck.com
- web github.com
- web disclosure@vulncheck.com