SSRF (Server-Side Request Forgery) in wwbn/avideo (CVE-2026-27732)
Summary
SSRF in wwbn/avideo (CVE-2026-27732). Risk of unauthorized operations or information disclosure. Exploitable via downloadURL. Mitigation: upgrade to 22.0 or later.
Original description
The description as published by the source.
Vulnerability Type
Authenticated Server-Side Request Forgery (SSRF)
Affected Product/Versions
AVideo versions prior to 22 (tested on AVideo 21.x).
Root Cause Summary
The aVideoEncoder.json.php API endpoint accepts a downloadURL parameter and fetches the referenced resource server-side without proper validation or an allow-list. This allows authenticated users to trigger server-side requests to arbitrary URLs (including internal network endpoints).
Impact Summary
An authenticated attacker can leverage SSRF to interact with internal services and retrieve sensitive data (e.g., internal APIs, metadata services), potentially leading to further compromise depending on the deployment environment.
Resolution/Fix
This issue has been fixed in AVideo version 22. Users should upgrade to version 22.0 as soon as possible.
Credits/Acknowledgement
Thanks to Arkadiusz Marta for responsibly reporting this issue.
- GitHub Profile: https://github.com/arkmarta/
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-27732 has been found in wwbn/avideo.
Attackers can target a specific entry point like downloadURL over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade wwbn/avideo to 22.0 or later.
If unsure, ask your IT team or search "wwbn/avideo CVE-2026-27732" on the vendor's site.
CVE-2026-27732 (wwbn/avideo) — CWE-918
Attack surface: downloadURL
Patched: 22.0 — 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 wwbn/avideo. Attackers reach the vulnerable code path via downloadURL.
Check the vendor advisory for the affected versions of wwbn/avideo. Attack surface: downloadURL.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 22.0.
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. Run grep -r 'wwbn/avideo' . 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 'wwbn/avideo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wwbn/avideoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade wwbn/avideo to 22.0ステージング環境で 22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com