SSRF (Server-Side Request Forgery) in lemmy_api_common (CVE-2026-42180)
Summary
SSRF in lemmy_api_common (CVE-2026-42180). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v3/post. Mitigation: upgrade to 0.19.18 or later.
Original description
The description as published by the source.
Lemmy is a link aggregator and forum for the fediverse. Prior to version 0.19.18, Lemmy allows an authenticated low-privileged user to create a link post through POST /api/v3/post. When a post is created in a public community, the backend asynchronously sends a Webmention to the attacker-controlled link target. The submitted URL is checked for syntax and scheme, but the audited code path does not reject loopback, private, or link-local destinations before the Webmention request is issued. This lets a normal user trigger server-side HTTP requests toward internal services. This issue has been patched in version 0.19.18.
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-42180 has been found in lemmy_api_common.
Attackers can target a specific entry point like POST /api/v3/post over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: upgrade lemmy_api_common to 0.19.18 or later.
If unsure, ask your IT team or search "lemmy_api_common CVE-2026-42180" on the vendor's site.
CVE-2026-42180 (lemmy_api_common) — CWE-918 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v3/post / url / http / https
Patched: 0.19.18 — 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 lemmy_api_common. Attackers reach the vulnerable code path via POST /api/v3/post.
Check the vendor advisory for the affected versions of lemmy_api_common. Attack surface: POST /api/v3/post / url / http / https.
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.19.18.
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/v3/post requests with malformed payloads or SQL meta-characters. Run grep -r 'lemmy_api_common' . 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 'lemmy_api_common' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
lemmy_api_commonを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/v3/post' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v3/postへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade lemmy_api_common to 0.19.18ステージング環境で 0.19.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v3/post on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com