CVE-2026-96655
Plex Media Server before 1.43.3.10861 allows an authenticated user to request arbitrary internal or external addresses via the '/video/:/transcode/universal' path parameter.
do firstUpgrade to a fixed release: 1.43.3.10861.
Can a WAF block it? Partly. The attack involves an authenticated user sending an HTTP request to a specific path with a parameter that allows requesting arbitrary addresses. This unusual use of the path parameter can be detected by a WAF rule matching that specific endpoint and parameter pattern. A WAF rule can match '/video/:/transcode/universal' path parameter with arbitrary address. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.
What a custom rule would match: '/video/:/transcode/universal' path parameter with arbitrary address
Also consider: patch · custom WAF rule · egress filter · IMDSv2
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2026-96655 being exploited?
Yes. CVE-2026-96655 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2026-96655?
CVE-2026-96655 is rated Medium with a CVSS score of 4.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-96655?
Yes. A fix has been recorded for CVE-2026-96655. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-96655 affect?
CVE-2026-96655 affects plex:media_server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 1.43.3.10861
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- partial
Assessed by CISA 20 Oct 2026 (SSVC 2.0.3).
timeline
- 23 Sept 2026Published
- 20 Oct 2026Added to CISA KEV (exploited in the wild) · 26 days later
- 20 Oct 2026CISA SSVC assessment: exploitation active · same day later
- 21 Oct 2026CVE record last updated · 1 day later
- 2 Nov 2026Analysed by vulneraibility.com · 13 days later
- 3 Nov 2026CISA remediation due date (US federal agencies) · same day later
- Advisoryraw.githubusercontent.com /cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-266-01.json
- Advisoryzmain.info /blog/plex2shell
- Linkforums.plex.tv /t/plex-media-server/30447/711
- Linkcve.org /CVERecord?id=CVE-2026-96655
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-96655
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.