Cross-Site Request Forgery (CSRF) in Nagios Core (CVE-2026-48551)
Summary
Vulnerability in Nagios Core (CVE-2026-48551). Data can be tampered with by attackers.
Original description
The description as published by the source.
Nagios Core before 4.5.14 and Nagios XI before 2026R1.7 contain a cross-site request forgery protection bypass via a self-supplied double-submit cookie. An attacker can supply matching cookie and request parameter values to bypass CSRF protection, enabling unauthenticated attackers to run commands as authorized users via malicious links.
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-48551 has been found in Nagios Core.
Data can be tampered with by attackers. CVSS score: 7.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Nagios Core CVE-2026-48551" on the vendor's site.
CVE-2026-48551 (Nagios Core) — CWE-352 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
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.
CSRF (CWE-352) exists in Nagios Core.
Check the vendor advisory for the affected versions of Nagios Core.
Severity: High (CVSS 7.4/10). Data can be tampered with by attackers.
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・依存マニフェストで Nagios Core を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-48551 nagios4 Fixed in: 4.4.6-4+deb12u2
- Ubuntu UBUNTU-CVE-2026-48551 nagios4
References
- web nvd.nist.gov
- web disclosure@vulncheck.com
- web nagios.com
- web disclosure@vulncheck.com
- web github.com
- web disclosure@vulncheck.com