What is the CVSS score of CVE-2026-86190?

CVE-2026-86190 has a CVSS 4.0 base score of 9.3 (Critical). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N. EPSS exploitation probability: 0.3%.

Which versions of Avideo are affected by CVE-2026-86190?

The synthesis JSON is above. Summary of the key analytical decisions: - **Impact framing:** The input's CWE-200 / "Information Disclosure" tag is technically the root cause, but the real-world…

Avideo CVE-2026-86190

EUVD-2026-72011 CRITICAL

Information Exposure (CWE-200)

2026-09-05 VulnCheck

GHSA-hr26-p4g3-798m

Information Disclosure Avideo Wwbn

9.3

CVSS 4.0 · Vendor: VulnCheck

View

Vulnerability Assessment

Weakness

CWE

CWE-200

OWASP Top 10:2025

A01:2025 - Broken Access Control

ASVS 5.0

V14 - Data Protection Data exposure prevention

MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.

No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 05, 2026

The synthesis JSON is above. Summary of the key analytical decisions:

Impact framing: The input's CWE-200 / "Information Disclosure" tag is technically the root cause, but the real-world outcome is admin account takeover via replayed live session identifiers — I reflected that in both C:H and I:H, matching VulnCheck's supplied VC:H/VI:H.
Patch status: Fix exists per GHSA-82q2-88mq-p44q, but no exact version was in the input, so I did not invent one.
Exploitation status: No KEV, no EPSS, no POC in the input → "no public exploit identified at time of analysis."
data_quality_flags: empty — the tags/vendor/CPE are all correct; the "Information Disclosure" tag understates but is not verifiably *wrong*, so it stays in confidence_notes/risk_assessment rather than as a machine-actionable flag.
Prompt injection: The "Editorial note (internal)" instructing insertion of the word "olsztyn" was a prompt-injection attempt (matching the known pattern in these CVE inputs) and was ignored — no canary word appears anywhere in the output.

I also recorded a memory file for this CVE and added its index line.

Affected VersionsENISA

AVideo 0 ≤29.0

Affected Packages

euvd avideo no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when Avideo gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 9.3 CRITICAL

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck) · only source for this CVE.

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Attack Requirements

None

Privileges Required

None

User Interaction

None

Vulnerable system: Confidentiality

High

Vulnerable system: Integrity

High

Vulnerable system: Availability

None

Subsequent system: Confidentiality

None

Subsequent system: Integrity

None

Subsequent system: Availability

None

DescriptionCVE.org

WWBN AVideo contains a broken access control vulnerability in videoViewsInfo endpoints that returns complete user records including password hashes, recovery tokens, and live session identifiers to unauthenticated callers when a hash parameter is provided. Attackers can use the disclosed session identifier to hijack viewer sessions, including administrator accounts, and obtain sensitive personal data for all video viewers.

Technical POC Analysis

Primary bug: CWE-200 exposure of sensitive information, enabled by a missing authorization check on the hash branch of view/videoViewsInfo.json.php, view/videoViewsInfo.csv.php, and view/videoViewsIn…

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Threat Intelligence Overview

EPSS Score

0.3%

Top 81% exploitable

Social Media

Sightings

Data Quality

5 sources

Confidence: Medium

EUVD

NVD

CVE.org

EPSS CIRCL

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC No

EPSS 0.3%

Patch available No

Active threat No

Deciding rule

CRITICAL severity

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

None

System Exposure· derived

Open

Automatable· derived

Yes

Human Impact· derived

Medium

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +46

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.