KODI A.I CyberSecurity Scoring
KODI
Company Information
Website:http://kodi.tv
Employees number:83
Number of followers:715
NAICS:5112
Industry Type:Software Development
Homepage:kodi.tv
KODI Risk Score (AI oriented)
Between 700 and 749
KODISoftware Development
Updated:
23/06/2026
23/06/2026
706/1000
Moderate
Ba
KODI Global Score (TPRM)
xxxx
KODISoftware Development
Score locked

KODIModerate
Current Score
706Ba (MODERATE)
01000
2 incidents
-5 avg impact
Incident timeline with MITRE ATT&CK tactics, techniques, and mitigations.
JUNE 2026
711
Vulnerability
23 Jun 2026 • KODI
FFmpeg, Nextcloud, Kodi, Immich and OBS Studio: Critical FFmpeg Vulnerability Enables Weaponized Media File Attacks
Critical FFmpeg Vulnerability (CVE-2026-8461) Enables Remote Code Execution via Malicious Media Files
706
CRITICAL-5
KODFFMIMPNEXPIX1782211302
Critical FFmpeg Vulnerability (CVE-2026-8461) Enables Remote Code Execution via Malicious Media Files
JFrog Security Research has uncovered a high-severity heap overflow vulnerability in FFmpeg’s MagicYUV decoder, tracked as CVE-2026-8461 (CVSS 8.8), which allows attackers to execute arbitrary code remotely by delivering a single crafted media file no authentication required.
The flaw, dubbed PixelSmash, resides in FFmpeg’s `libavcodec` and stems from a rounding mismatch in how the frame allocator and MagicYUV decoder calculate chroma plane heights for subsampled pixel formats like YUV420P. By manipulating a `slice_height` value in a malicious bitstream, attackers can trigger out-of-bounds heap writes, overwriting critical memory structures. Specifically, the exploit targets FFmpeg’s `AVBuffer` struct, replacing a function pointer (`buf->free`) with the address of `system()` and injecting a shell command via `buf->opaque`, turning frame cleanup into an arbitrary command execution vector.
JFrog demonstrated full remote code execution (RCE) on two platforms using a 50 KB crafted AVI file:
- Jellyfin 10.11.9: Automatically triggered when a malicious file is placed in a monitored library folder, exploiting the media scan pipeline.
- Nextcloud: Executes commands as `www-data` when a user browses the Files view, leveraging the Movie preview provider.
A particularly high-risk attack vector is the torrent-to-media-library pipeline, where Jellyfin users configure torrent clients to download directly into monitored folders. The exploit requires no user interaction beyond the initial download, as FFmpeg’s real-time filesystem monitor automatically processes the file.
As FFmpeg is the most widely deployed media processing framework, the impact is vast. The MagicYUV decoder is enabled by default in upstream FFmpeg builds and major Linux distributions, including Ubuntu, Debian, Fedora, Arch, and Alpine. Confirmed affected applications include:
- Media players: mpv, Kodi, OBS Studio
- File managers: GNOME, KDE, XFCE (via `ffmpegthumbnailer`)
- Media servers: Jellyfin, Emby, Nextcloud, Immich, PhotoPrism
- AI/ML pipelines: vLLM (crashed in all tested instances)
The exploit works across AVI, MKV, and MOV containers. Only Plex remains unaffected due to its use of a minimal FFmpeg build with `--disable-decoders` and a strict codec allow-list.
Mitigation requires upgrading to FFmpeg 9.0 or later. For systems unable to update immediately, workarounds include:
- Rebuilding FFmpeg with `--disable-decoder=magicyuv`
- Applying a 7-line patch to `libavcodec/magicyuv.c` that enforces `slice_height` validation
The FFmpeg and Jellyfin security teams have acknowledged the disclosure and released fixes. Exposure can be checked by running:
```sh
ffmpeg -decoders 2>/dev/null | grep magicyuv
```
A vulnerable system will return `VFS..D magicyuv`.
INCIDENT DETAILS -
TYPE
IMPACT
REFERENCES
MAY 2026
710
APRIL 2026
709
MARCH 2026
709
FEBRUARY 2026
708
JANUARY 2026
707
DECEMBER 2025
706
NOVEMBER 2025
705
OCTOBER 2025
704
SEPTEMBER 2025
703
AUGUST 2025
702
JULY 2025
701
APRIL 2023
753
Breach
01 Apr 2023 • KODI
KODI
Kodi Data Breach
662
MEDIUM-91
KOD23729523
Kodi has disclosed a data breach, threat actors have stolen the company’s MyBB forum database that contained data for over 400K users and private messages.
The BreachForums cybercrime site, which was recently shut down by law authorities, was another place where the threat actors tried to sell the stolen data.
After creating database backups that were later downloaded and deleted, the threat actors exploited the account improperly.
The administrative team performed an initial inspection of the portion of the infrastructure that was accessible by the attackers and then disabled the account used in the data breach to keep the invaders out.
The company has taken the forum offline while securing its infrastructure.
INCIDENT DETAILS -
TYPE
MOTIVATION
IMPACT
DATA BREACH
REFERENCES
Frequently Asked Questions
?
What is the current A.I Rankiteo Cyber Score for KODI ??
What was KODI's A.I Rankiteo Cyber Score in May 2026 ??
What was KODI's A.I Rankiteo Cyber Score in April 2026 ??
What was KODI's A.I Rankiteo Cyber Score in March 2026 ??
What was KODI's A.I Rankiteo Cyber Score in February 2026 ??
What was KODI's A.I Rankiteo Cyber Score in January 2026 ??
What was KODI's A.I Rankiteo Cyber Score in December 2025 ??
What was KODI's A.I Rankiteo Cyber Score in November 2025 ??
What was KODI's A.I Rankiteo Cyber Score in October 2025 ??
What was KODI's A.I Rankiteo Cyber Score in September 2025 ??
What was KODI's A.I Rankiteo Cyber Score in August 2025 ??
What was KODI's A.I Rankiteo Cyber Score in July 2025 ??
What is the average per-incident point impact on KODI's A.I Rankiteo Cyber Score over the past 12 months ??
Where can I access detailed records of all cyber incidents associated with KODI ??
Where can I find a summary of the A.I Rankiteo Risk Scoring methodology ??
Where can I view KODI's profile page on Rankiteo ??
How accurate is the A.I Rankiteo Risk Scoring methodology ?