SSRF (Server-Side Request Forgery) in kolibri (CVE-2026-48053)
Summary
SSRF in kolibri (CVE-2026-48053). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/auth/remotefacilityuser. Mitigation: upgrade to 0.19.4 or later.
Original description
The description as published by the source.
Kolibri is an offline-first education platform. Prior to version 0.19.4, several Kolibri API endpoints accept an unvalidated baseurl parameter and fetch attacker-controlled URLs from the Kolibri server, reflecting the response body back to the caller. The original report identified two endpoints on the RemoteFacilityUser* viewsets; remediation review found two further reflection points on the same pattern. The GET endpoint was unauthenticated. Version 0.19.4 fixes the vulnerability.
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-48053 has been found in kolibri.
Attackers can target a specific entry point like GET /api/auth/remotefacilityuser over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: upgrade kolibri to 0.19.4 or later.
If unsure, ask your IT team or search "kolibri CVE-2026-48053" on the vendor's site.
CVE-2026-48053 (kolibri) — CWE-918 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/auth/remotefacilityuser / POST /api/auth/remotefacilityauthenticateduserinfo / POST /api/public/setupwizard/loddata / GET /api/public/networklocation/
Patched: 0.19.4 — 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 kolibri. Attackers reach the vulnerable code path via GET /api/auth/remotefacilityuser without authentication.
Check the vendor advisory for the affected versions of kolibri. Attack surface: GET /api/auth/remotefacilityuser / POST /api/auth/remotefacilityauthenticateduserinfo / POST /api/public/setupwizard/loddata / GET /api/public/networklocation/.
Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.
Update to 0.19.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/auth/remotefacilityuser requests with malformed payloads or SQL meta-characters. Run grep -r 'kolibri' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'kolibri' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
kolibriを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/auth/remotefacilityuser' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/auth/remotefacilityuserへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade kolibri to 0.19.4ステージング環境で 0.19.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/auth/remotefacilityuser on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com