AVideo through 29.0 contains a blind server-side request forgery vulnerability in the getHeaderContentTypeFromURL function that issues get_headers() calls guarded only by format validation. Authenticated users with canUpload permission can store attacker-chosen URLs as video links, triggering vulnerable function execution on every video watch page render to probe internal hosts using content-type oracles and timing-based detection.
CVE-2026-91967
Score 5.0 from GitHub Security Advisory published 2026-09-15. a secondary CVSS source baseline 5.0; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.0
- EG Score
- 5.0(high)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity50% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 15, 2026AVideo through 29.0 Blind SSRF via getHeaderContentTypeFromURL | Advisories | VulnCheck
https://www.vulncheck.com/advisories/avideo-through-29.0-blind-ssrf-via-getheadercontenttypefromurlAuthenticated blind SSRF via stored videoLink get_headers() in getHeaderContentTypeFromURL · Advisory · WWBN/AVideo · GitHub
https://github.com/WWBN/AVideo/security/advisories/GHSA-vjgr-5x63-cq96Vendor Advisories for CVE-2026-91967(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 22× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-21 09:38 UTCEG score recompute
- 2026-09-21 09:38 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 11:50 UTCEG score recompute
- 2026-09-20 11:50 UTCGHSA enrichment
- 2026-09-19 13:59 UTCEG score recompute
- 2026-09-19 13:59 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 16:08 UTCEG score recompute
- 2026-09-18 16:08 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 18:08 UTCEG score recompute
- 2026-09-17 18:08 UTCGHSA enrichment
- 2026-09-17 15:29 UTCEG score recompute
- 2026-09-17 15:29 UTCGHSA enrichment
- 2026-09-16 21:07 UTCGHSA enrichment
- 2026-09-16 14:21 UTCEG score recompute
- 2026-09-16 14:21 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-15 16:32 UTCEG score recompute
- 2026-09-15 15:23 UTCEG score recompute
- 2026-09-15 15:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-91967?
When was CVE-2026-91967 disclosed?
Is CVE-2026-91967 actively exploited?
What is the CVSS score of CVE-2026-91967?
How do I remediate CVE-2026-91967?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-91967
Is Your Infrastructure Affected by CVE-2026-91967?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.