5.x merge 4.x - #1261
Merged
Merged
Conversation
The i686 build was the only architecture still pinning the old ffmpeg 5.1.4 (libavcodec.so.59); every other arch/libc combination (manylinux_2_28, manylinux2014 x86_64/aarch64, musllinux_1_2) already builds ffmpeg 8.1.1. This aligns i686 with the rest and pulls in the security fixes tracked in opencv#1212 and opencv#1228. Verified: ffmpeg-8.1.1.tar.bz2 is published at the same release URL the recipe uses, and all ffmpeg configure flags in this recipe (--enable-openssl/libvpx/shared/pic) remain valid in 8.1.1. The i686 toolchain (NASM 2.15.04, OpenSSL 1.1.1w) matches the x86_64 recipe that already ships 8.1.1, so build dependencies are unchanged.
Bump ffmpeg to 8.1.1 in manylinux2014 i686 build
…te_4.x Standard github actions stetps update.
…st_4.x Numpy package update for testing on Linux
Submodules update to OpenCV 4.14.0
…ve-2026-8461 Bump ffmpeg to 8.1.2 to fix CVE-2026-8461 opencv#1249 Resolves opencv#1248. ### Problem ffmpeg `8.1.1` is affected by **[CVE-2026-8461](https://nvd.nist.gov/vuln/detail/CVE-2026-8461)** - an out-of-bounds write in the MagicYUV decoder (`libavcodec/magicyuv.c`), CWE-787, CVSS 3.1 base score **8.8 (HIGH)**. It allows denial of service and potentially remote code execution when decoding a crafted MagicYUV stream. It is fixed upstream in ffmpeg `8.1.2`. ### Change Bump `FFMPEG_VERSION` from `8.1.1` to `8.1.2` in all seven build Dockerfiles: | Image | Arch | |---|---| | manylinux2014 | i686, x86_64, aarch64 | | manylinux_2_28 | x86_64, aarch64 | | musllinux_1_2 | x86_64, aarch64 | One line per file, no other changes. `8.1.1` appears nowhere else in the tree, so there are no checksums or pins left to update. ### Notes - `ffmpeg-8.1.2.tar.gz` is published on ffmpeg.org, so the existing download URLs in each Dockerfile resolve unchanged with no other edits. `8.1.3` is not released, making `8.1.2` the correct target. - `8.1.2` is a patch release in the same `8.1` series as the currently pinned version, so no API or ABI change is expected for the OpenCV video I/O backend. - Follows the same pattern as opencv#1233, which bumped the i686 image to `8.1.1`.
Fix VideoCapture not able to read AV1 encoded files on Linux opencv#1209 Hi, this is an attempt to fix opencv#908 as AV1 encoded files are pretty common nowadays. My assumption is that there is no av1 decoder available in the official wheel as the same works just fine using opencv-python from ArchLinux build against their ffmpeg build. On Windows av1 decoding works but not on Linux using the official wheels. I am not sure but I assume there is some kind of fallback mechanism which then uses Windows-native frameworks for decoding which is not available on Linux hence it fails on Linux using ffmpeg backend. Didn't adjust the arm images yet, wanted to get some feedback first if I'm going in the right direction here. Waiting for the CI to run through to create a wheel I can test if this actually fixes the issue 🤞 edit: looks like CI doesn't run without approval by maintainers, so changed to ready-for-review fixes: opencv#1205 fixes: opencv#908
Fixed path for release.
|
Hi @asmorkalov . Thanks for taking care of this! |
Collaborator
Author
|
No date for now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.