Register | Log in

docker-registry

Docker toolset to pack, ship, store, and deliver content

Choose email to subscribe with

general

source: docker-registry (main)
version: 2.8.3+ds1-2
maintainer: Debian Go Packaging Team (DMD)
uploaders: Tianon Gravi [DMD] – Dmitry Smirnov [DMD]
arch: all any
std-ver: 4.7.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.7.1+ds2-7+deb11u1
o-o-sec: 2.7.1+ds2-7+deb11u1
oldstable: 2.8.2+ds1-1
stable: 2.8.3+ds1-2
testing: 2.8.3+ds1-2
unstable: 2.8.3+ds1-2

versioned links

2.7.1+ds2-7+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.8.2+ds1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.8.3+ds1-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

docker-registry (2 bugs: 0, 1, 1, 0)
golang-github-docker-distribution-dev

action needed

A new upstream version is available: 3.1.0 high

A new upstream version 3.1.0 is available, you should consider packaging it.

Created: 2025-11-27 Last update: 2026-04-25 10:00

2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:

CVE-2026-33540: Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, in pull-through cache mode, distribution discovers token auth endpoints by parsing WWW-Authenticate challenges returned by the configured upstream registry. The realm URL from a bearer challenge is used without validating that it matches the upstream registry host. As a result, an attacker-controlled upstream (or an attacker with MitM position to the upstream) can cause distribution to send the configured upstream credentials via basic auth to an attacker-controlled realm URL. This vulnerability is fixed in 3.1.0.
CVE-2026-35172: Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.

Created: 2026-04-12 Last update: 2026-04-22 10:48

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2026-33540: Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, in pull-through cache mode, distribution discovers token auth endpoints by parsing WWW-Authenticate challenges returned by the configured upstream registry. The realm URL from a bearer challenge is used without validating that it matches the upstream registry host. As a result, an attacker-controlled upstream (or an attacker with MitM position to the upstream) can cause distribution to send the configured upstream credentials via basic auth to an attacker-controlled realm URL. This vulnerability is fixed in 3.1.0.
CVE-2026-35172: Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.

Created: 2026-04-12 Last update: 2026-04-22 10:48

2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:

CVE-2026-33540: Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, in pull-through cache mode, distribution discovers token auth endpoints by parsing WWW-Authenticate challenges returned by the configured upstream registry. The realm URL from a bearer challenge is used without validating that it matches the upstream registry host. As a result, an attacker-controlled upstream (or an attacker with MitM position to the upstream) can cause distribution to send the configured upstream credentials via basic auth to an attacker-controlled realm URL. This vulnerability is fixed in 3.1.0.
CVE-2026-35172: Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.

Created: 2026-04-12 Last update: 2026-04-22 10:48

2 security issues in bullseye high

There are 2 open security issues in bullseye.

2 important issues:

CVE-2026-33540: Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, in pull-through cache mode, distribution discovers token auth endpoints by parsing WWW-Authenticate challenges returned by the configured upstream registry. The realm URL from a bearer challenge is used without validating that it matches the upstream registry host. As a result, an attacker-controlled upstream (or an attacker with MitM position to the upstream) can cause distribution to send the configured upstream credentials via basic auth to an attacker-controlled realm URL. This vulnerability is fixed in 3.1.0.
CVE-2026-35172: Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.

Created: 2026-04-12 Last update: 2026-04-22 10:48

2 security issues in bookworm high

There are 2 open security issues in bookworm.

2 important issues:

CVE-2026-33540: Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, in pull-through cache mode, distribution discovers token auth endpoints by parsing WWW-Authenticate challenges returned by the configured upstream registry. The realm URL from a bearer challenge is used without validating that it matches the upstream registry host. As a result, an attacker-controlled upstream (or an attacker with MitM position to the upstream) can cause distribution to send the configured upstream credentials via basic auth to an attacker-controlled realm URL. This vulnerability is fixed in 3.1.0.
CVE-2026-35172: Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.

Created: 2026-04-12 Last update: 2026-04-22 10:48

1 bug tagged help in the BTS normal

The BTS contains 1 bug tagged help, please consider helping the maintainer in dealing with it.

Created: 2024-08-31 Last update: 2026-04-25 14:00

4 new commits since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit 5b523d1f692bd2d50b4657564628faa2e50d9801
Author: Reinhard Tartler <siretart@tauware.de>
Date:   Mon Sep 2 07:25:27 2024 -0400

    Update changelog for 2.8.3+ds1-2 release

commit 0e5a86d6bdfecdfba362e529208650ab531cb5f0
Author: Reinhard Tartler <siretart@tauware.de>
Date:   Mon Sep 2 07:25:13 2024 -0400

    Add missing dependency on golang-github-distribution-reference-dev
    
    Fixes build failures in dependent packages

commit 14670af44d5552d071ef3ba5a542c888d1fc32ed
Author: Reinhard Tartler <siretart@tauware.de>
Date:   Mon Sep 2 07:24:01 2024 -0400

    Normalize fields with wrap-and-sort

commit de92948650d435bb361de212e05f6e45dea6cce6
Author: Reinhard Tartler <siretart@tauware.de>
Date:   Sat Aug 31 11:54:03 2024 -0400

    Remove Arnaud and Tim from Uploaders field
    
    both email addresses are currently bouncing

Created: 2024-08-31 Last update: 2026-04-18 15:01

lintian reports 1 warning normal

Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.

Created: 2025-04-10 Last update: 2025-04-10 09:30

debian/patches: 3 patches to forward upstream low

Among the 9 debian patches available in version 2.8.3+ds1-2 of the package, we noticed the following issues:

3 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2024-09-02 23:00

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.0).

Created: 2025-02-21 Last update: 2026-03-31 15:01

news

[2024-09-05] docker-registry 2.8.3+ds1-2 MIGRATED to testing (Debian testing watch)
[2024-09-02] Accepted docker-registry 2.8.3+ds1-2 (source) into unstable (Reinhard Tartler)
[2024-08-31] Accepted docker-registry 2.8.3+ds1-1 (source) into unstable (Reinhard Tartler)
[2023-06-28] Accepted docker-registry 2.6.2~ds1-2+deb10u1 (source) into oldoldstable (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
[2023-05-29] Accepted docker-registry 2.7.1+ds2-7+deb11u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Shengjing Zhu)
[2023-05-27] Accepted docker-registry 2.7.1+ds2-7+deb11u1 (source) into stable-security (Debian FTP Masters) (signed by: Shengjing Zhu)
[2023-05-19] docker-registry 2.8.2+ds1-1 MIGRATED to testing (Debian testing watch)
[2023-05-13] Accepted docker-registry 2.8.2+ds1-1 (source) into unstable (Shengjing Zhu)
[2022-07-03] docker-registry 2.8.1+ds1-2 MIGRATED to testing (Debian testing watch)
[2022-06-29] Accepted docker-registry 2.8.1+ds1-2 (source) into unstable (Jelmer Vernooĳ) (signed by: Jelmer Vernooij)
[2022-03-29] docker-registry 2.8.1+ds1-1 MIGRATED to testing (Debian testing watch)
[2022-03-27] Accepted docker-registry 2.8.1+ds1-1 (source) into unstable (Shengjing Zhu)
[2022-02-13] docker-registry 2.8.0+ds1-4 MIGRATED to testing (Debian testing watch)
[2022-02-11] Accepted docker-registry 2.8.0+ds1-4 (source) into unstable (Shengjing Zhu)
[2022-02-10] Accepted docker-registry 2.8.0+ds1-3 (source) into unstable (Shengjing Zhu)
[2022-02-08] Accepted docker-registry 2.8.0+ds1-2 (source) into experimental (Shengjing Zhu)
[2022-02-07] Accepted docker-registry 2.8.0+ds1-1 (source) into experimental (Shengjing Zhu)
[2020-01-15] docker-registry 2.7.1+ds2-7 MIGRATED to testing (Debian testing watch)
[2020-01-07] Accepted docker-registry 2.7.1+ds2-7 (source) into unstable (Arnaud Rebillout)
[2020-01-07] Accepted docker-registry 2.7.1+ds2-6 (source) into unstable (Arnaud Rebillout)
[2019-12-19] docker-registry 2.7.1+ds2-5 MIGRATED to testing (Debian testing watch)
[2019-12-17] docker-registry 2.7.1~ds1-4 MIGRATED to testing (Debian testing watch)
[2019-12-17] Accepted docker-registry 2.7.1+ds2-5 (source) into unstable (Arnaud Rebillout) (signed by: Dmitry Smirnov)
[2019-12-15] Accepted docker-registry 2.7.1~ds1-4 (source) into unstable (Dmitry Smirnov)
[2019-11-05] Accepted docker-registry 2.7.1~ds1-3 (source) into unstable (Arnaud Rebillout) (signed by: Dmitry Smirnov)
[2019-10-01] docker-registry 2.7.1~ds1-2 MIGRATED to testing (Debian testing watch)
[2019-09-13] Accepted docker-registry 2.7.1~ds1-2 (source) into unstable (Dmitry Smirnov)
[2019-09-12] Accepted docker-registry 2.7.1~ds1-1 (source) into unstable (Dmitry Smirnov)
[2018-06-06] docker-registry 2.6.2~ds1-2 MIGRATED to testing (Debian testing watch)
[2018-05-06] Accepted docker-registry 2.6.2~ds1-2 (source amd64 all) into unstable (Dmitry Smirnov)

1
2

bugs [bug history graph]

all: 3
RC: 0
I&N: 2
M&W: 1
F&P: 0
patch: 0
help: 1

links

homepage
lintian (0, 1)
buildd: logs, reproducibility, cross
popcon
browse source code
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.8.3+ds1-2build1
3 bugs

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers

Report problems to the tracker.debian.org pseudo-package in the Debian BTS.

Documentation — Bugs — Git Repository — Contributing