Skip to content

fix: Docker Redis CVE-2025-49844 — fix build failures and version pinning (#1671)#1846

Closed
hafezparast wants to merge 1 commit intounclecode:developfrom
hafezparast:fix/maysam-redis-dockerfile-1671
Closed

fix: Docker Redis CVE-2025-49844 — fix build failures and version pinning (#1671)#1846
hafezparast wants to merge 1 commit intounclecode:developfrom
hafezparast:fix/maysam-redis-dockerfile-1671

Conversation

@hafezparast
Copy link

Summary

Changes

  • Dockerfile:
    • Added pre-install of curl and gnupg before Redis repo setup
    • Pin redis-tools to same version as redis-server
    • Added apt-mark hold redis-server redis-tools to prevent upgrades
    • Updated default version to 7.2.13 (latest 7.2.x patch)

Verified locally

$ docker build --target build -t crawl4ai-redis-test .
$ docker run --rm crawl4ai-redis-test redis-server --version
Redis server v=7.2.13
$ docker run --rm crawl4ai-redis-test apt-mark showhold
redis-server
redis-tools

Test plan

  • New test suite: tests/test_issue_1671_redis_cve.py (10 tests)
  • Regression suite: 304/305 passing (1 pre-existing HuggingFace failure)
  • Full Docker build verified locally — Redis 7.2.13 survives playwright install --with-deps

Generated with Claude Code

…ning (unclecode#1671)

The previous Redis CVE fix on develop had three issues:
1. curl/gnupg used before being installed (build failure on slim image)
2. redis-tools not pinned alongside redis-server (apt dependency conflict)
3. Packages not held, so playwright install --with-deps upgraded Redis to 8.x

Now installs curl/gnupg first, pins both redis-server and redis-tools to
7.2.13, and uses apt-mark hold to prevent subsequent upgrades.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@ntohidi
Copy link
Collaborator

ntohidi commented Mar 22, 2026

Thank you for your contribution, this is already fixed and it's in the latest Docker image: 0.8.5
will be in the mian branch soon

@ntohidi ntohidi closed this Mar 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants