SSRF (Server-Side Request Forgery) in Nextcloud News (CVE-2026-44515)
Summary
SSRF in Nextcloud News (CVE-2026-44515). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 28.3.0-beta.1 or later.
Original description
The description as published by the source.
Nextcloud News is an RSS/Atom feed reader. Prior to 28.3.0-beta.1, Nextcloud News allows authenticated users to add feeds by providing a feed URL (via the web interface or the API). In affected versions, an authenticated attacker could provide a URL pointing to internal/private IP ranges or localhost, causing the Nextcloud server to perform server-side HTTP requests to attacker-controlled destinations, but not relaying the result. This enables blind SSRF, which can be used to scan or probe internal network services that are reachable from the Nextcloud server. This vulnerability is fixed in 28.3.0-beta.1.
Source: NIST National Vulnerability Database NVD
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-44515 has been found in Nextcloud News.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Nextcloud News to 28.3.0-beta.1 or later.
If unsure, ask your IT team or search "Nextcloud News CVE-2026-44515" on the vendor's site.
CVE-2026-44515 (Nextcloud News) — CWE-918
Patched: 28.3.0-beta.1 — apply immediately
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.
SSRF (CWE-918) exists in Nextcloud News.
Check the vendor advisory for the affected versions of Nextcloud News.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 28.3.0-beta.1.
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・依存マニフェストで Nextcloud News を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Nextcloud News to 28.3.0-beta.1ステージング環境で 28.3.0-beta.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。