curl - Debian Package Tracker

general

source: curl (main)
version: 8.23.0-1
maintainer: Debian Curl Maintainers (DMD)
uploaders: Sergio Durigan Junior [DMD] – Samuel Henrique [DMD] – Carlos Henrique Lima Melara [DMD]
arch: all any
std-ver: 4.7.4
VCS: Git (Browse, QA)

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

[pool directory]

o-o-stable: 7.74.0-1.3+deb11u13
o-o-sec: 7.74.0-1.3+deb11u16
o-o-p-u: 7.74.0-1.3+deb11u13
oldstable: 7.88.1-10+deb12u15
old-sec: 7.88.1-10+deb12u5
old-bpo: 8.14.1-2+deb13u2~bpo13+1
old-p-u: 7.88.1-10+deb12u15
stable: 8.14.1-2+deb13u4
stable-sec: 8.14.1-2+deb13u7
stable-bpo: 8.21.0-2~bpo13+1
stable-p-u: 8.14.1-2+deb13u7
testing: 8.22.0-1
unstable: 8.23.0-1

versioned links

7.74.0-1.3+deb11u13: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
7.74.0-1.3+deb11u16: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
7.88.1-10+deb12u5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
7.88.1-10+deb12u15: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
8.14.1-2+deb13u2~bpo13+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
8.14.1-2+deb13u4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
8.14.1-2+deb13u7: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
8.20.0-5~bpo13+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
8.21.0-2~bpo13+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
8.22.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
8.23.0~rc3-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
8.23.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

curl (32 bugs: 0, 21, 11, 0)
libcurl3t64-gnutls
libcurl4-doc
libcurl4-gnutls
libcurl4-gnutls-dev
libcurl4-openssl-dev (4 bugs: 0, 4, 0, 0)
libcurl4t64

action needed

Debci reports failed tests high

unstable: fail (log)
The tests ran in 0:22:33
Last run: 2026-08-17T08:16:43.000Z
Previous status: unknown

testing: pass (log)
The tests ran in 0:20:15
Last run: 2026-10-15T12:53:56.000Z
Previous status: unknown

stable: pass (log)
The tests ran in 0:10:17
Last run: 2026-09-17T11:55:46.000Z
Previous status: unknown

Created: 2026-07-09 Last update: 2026-10-18 09:31

20 security issues in forky high

There are 20 open security issues in forky.

20 important issues:

CVE-2026-86410:
CVE-2026-86412:
CVE-2026-86413:
CVE-2026-86414:
CVE-2026-86415:
CVE-2026-87861:
CVE-2026-87862:
CVE-2026-87863:
CVE-2026-87865:
CVE-2026-92386:
CVE-2026-92387:
CVE-2026-92388:
CVE-2026-92389:
CVE-2026-92390:
CVE-2026-92391:
CVE-2026-92392: During an upload, curl mishandles HTTP/2 `RST_STREAM` received from the server (with reason `HTTP_1_1_REQUIRED` or `REFUSED_STREAM`) leading to a use after free of a `struct Curl_easy` object.
CVE-2026-94265:
CVE-2026-94266:
CVE-2026-107928:
CVE-2026-107929:

Created: 2026-10-14 Last update: 2026-10-15 05:00

30 security issues in bookworm high

There are 30 open security issues in bookworm.

11 important issues:

CVE-2026-86409:
CVE-2026-86410:
CVE-2026-86414:
CVE-2026-87864:
CVE-2026-87865:
CVE-2026-92388:
CVE-2026-92389:
CVE-2026-92390:
CVE-2026-92391:
CVE-2026-94266:
CVE-2026-107928:

19 issues postponed or untriaged:

CVE-2026-1965: (needs triaging) libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request. libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criterion must first be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. One underlying reason being that Negotiate sometimes authenticates *connections* and not *requests*, contrary to how HTTP is designed to work. An application that allows Negotiate authentication to a server (that responds wanting Negotiate) with `user1:password1` and then does another operation to the same server also using Negotiate but with `user2:password2` (while the previous connection is still alive) - the second request wrongly reused the same connection and since it then sees that the Negotiate negotiation is already made, it sends the request over that connection thinking it uses the user2 credentials when it is in fact still using the connection authenticated for user1... The set of authentication methods to use is set with `CURLOPT_HTTPAUTH`. Applications can disable libcurl's reuse of connections and thus mitigate this problem, by using one of the following libcurl options to alter how connections are or are not reused: `CURLOPT_FRESH_CONNECT`, `CURLOPT_MAXCONNECTS` and `CURLMOPT_MAX_HOST_CONNECTIONS` (if using the curl_multi API).
CVE-2026-4873: (needs triaging) A vulnerability exists where a connection requiring TLS incorrectly reuses an existing unencrypted connection from the same connection pool. If an initial transfer is made in clear-text (via IMAP, SMTP, or POP3), a subsequent request to that same host bypasses the TLS requirement and instead transmit data unencrypted.
CVE-2026-5545: (needs triaging) libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials when it is in fact still using the connection authenticated for user1...
CVE-2026-6253: (needs triaging) curl might erroneously pass on credentials for a first proxy to a second proxy. This can happen when the following conditions are true: 1. curl is setup to use specific different proxies for different URL schemes 2. the first proxy needs credentials 3. the second proxy uses no credentials 4. while using the first proxy (using say `http://`), curl is asked to follow a redirect to a URL using another scheme (say `https://`), accessed using a second, different, proxy
CVE-2026-6276: (needs triaging) Using libcurl, when a custom `Host:` header is first set for an HTTP request and a second request is subsequently done using the same *easy handle* but without the custom `Host:` header set, the second request would use stale information and pass on cookies meant for the first host in the second request. Leak them.
CVE-2026-6429: (needs triaging) When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, libcurl could leak the password used for the first host to the followed-to host under certain circumstances.
CVE-2026-8286: (postponed; to be fixed through a stable update) A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.
CVE-2026-8458: (postponed; to be fixed through a stable update) libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different "services". libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different services.
CVE-2026-8924: (postponed; to be fixed through a stable update) A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set "super cookies" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.
CVE-2026-8927: (postponed; to be fixed through a stable update) When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent transfer routed through `proxyB` erroneously leaks the `Proxy-Authorization:` header intended solely for `proxyA`.
CVE-2026-8932: (postponed; to be fixed through a stable update) libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them match too easily. In particular options related to the private key.
CVE-2026-10536: (postponed; to be fixed through a stable update) A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or `CURLOPT_STREAM_DEPENDS_E`, subsequently invokes `curl_easy_reset()`, and finally terminates the handle with `curl_easy_cleanup()`. During this final cleanup phase, libcurl attempts to access and modify an internal structure that was already freed during the reset operation.
CVE-2026-11856: (postponed; to be fixed through a stable update) Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Authorization:` header field meant for `hostA`, to `hostB`.
CVE-2026-12064: (postponed; to be fixed through a stable update) When a user invokes curl using a schemeless URL combined with `--proto-default` sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical SSH security options like CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the libcurl runtime successfully honors CURLOPT_DEFAULT_PROTOCOL and establishes the connection via SFTP/SCP as specified. Because the tool layer skipped the security configuration, these SSH host verification options are silently omitted, causing curl to connect to an unverified SSH remote host without throwing an error.
CVE-2026-13608: (postponed; to be fixed through a stable update) A flaw in the libcurl SASL negotiation for LDAP authentication allows an incomplete handshake sequence to be misinterpreted as a successful cryptographic verification. An attacker executing a Man-in-the-Middle (MITM) attack can inject a premature or shortcut response that bypasses complete peer validation.
CVE-2026-18924: (postponed; to be fixed through a stable update) A flaw in libcurl's handling of HTTP/2 Server Push streams, when the parent handle is set to share connections with other handles, can lead to use-after-free in the cleanup process.
CVE-2026-19931: (postponed; to be fixed through a stable update) A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given hostname using Negotiate authentication, when the initial request is done using empty credentials. This can make user B's request get sent over user A's previously authenticated connection.
CVE-2026-80230: (postponed; to be fixed through a stable update) When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and `CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.
CVE-2026-82209: (postponed; to be fixed through a stable update) When libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a `Set-Cookie` header where the `Domain` attribute explicitly matches an origin host that is itself a public suffix (e.g., `Domain=co.uk` set by `co.uk`). Instead of coercing it into a strict host-only cookie, libcurl saves the cookie with wildcard domain scope (`.co.uk`). Consequently, the cookie is inappropriately included in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix (e.g., `attacker.co.uk`).

Created: 2026-10-14 Last update: 2026-10-15 05:00

The package has not entered testing even though the delay is over normal

The package has not entered testing even though the 2-day delay is over. Check why.

Created: 2026-10-16 Last update: 2026-10-18 10:20

9 bugs tagged patch in the BTS normal

The BTS contains patches fixing 9 bugs (10 if counting merged bugs), consider including or untagging them.

Created: 2026-09-02 Last update: 2026-10-18 10:18

1 new commit 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 45864989aea51a377b823a225ca1d25ebe517ac8
Author: Samuel Henrique <samueloph@debian.org>
Date:   Wed Oct 14 19:34:15 2026 -0700

    d/t/common-pytest-http: Build dnsd for tests

Created: 2026-10-15 Last update: 2026-10-15 04:31

lintian reports 5 warnings normal

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

Created: 2026-09-24 Last update: 2026-09-24 17:01

32 low-priority security issues in trixie low

There are 32 open security issues in trixie.

32 issues left for the package maintainer to handle:

CVE-2026-8458: (needs triaging) libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different "services". libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different services.
CVE-2026-8926: (needs triaging) When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username (without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netrc` file for that host if such a one exists and there is no match for the specified user.
CVE-2026-8932: (needs triaging) libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them match too easily. In particular options related to the private key.
CVE-2026-9079: (needs triaging) libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.
CVE-2026-9080: (needs triaging) Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION` callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer's memory has been freed.
CVE-2026-9545: (needs triaging) In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate. When libcurl returns to the hostname the second time with a cached SSL session (`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the `CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might send off the second request's bytes on that new connection *before* enforcing the certificate verification failure. Potentially leaking sensitive information.
CVE-2026-10536: (needs triaging) A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or `CURLOPT_STREAM_DEPENDS_E`, subsequently invokes `curl_easy_reset()`, and finally terminates the handle with `curl_easy_cleanup()`. During this final cleanup phase, libcurl attempts to access and modify an internal structure that was already freed during the reset operation.
CVE-2026-11856: (needs triaging) Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Authorization:` header field meant for `hostA`, to `hostB`.
CVE-2026-12064: (needs triaging) When a user invokes curl using a schemeless URL combined with `--proto-default` sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical SSH security options like CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the libcurl runtime successfully honors CURLOPT_DEFAULT_PROTOCOL and establishes the connection via SFTP/SCP as specified. Because the tool layer skipped the security configuration, these SSH host verification options are silently omitted, causing curl to connect to an unverified SSH remote host without throwing an error.
CVE-2026-13608: (needs triaging) A flaw in the libcurl SASL negotiation for LDAP authentication allows an incomplete handshake sequence to be misinterpreted as a successful cryptographic verification. An attacker executing a Man-in-the-Middle (MITM) attack can inject a premature or shortcut response that bypasses complete peer validation.
CVE-2026-18924: (needs triaging) A flaw in libcurl's handling of HTTP/2 Server Push streams, when the parent handle is set to share connections with other handles, can lead to use-after-free in the cleanup process.
CVE-2026-19931: (needs triaging) A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given hostname using Negotiate authentication, when the initial request is done using empty credentials. This can make user B's request get sent over user A's previously authenticated connection.
CVE-2026-80229: (needs triaging) When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.
CVE-2026-80230: (needs triaging) When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and `CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.
CVE-2026-80255: (needs triaging) A `Set-Cookie:` header using tab (horizontal tab, ASCII code 9) instead of space (ascii code 32) immediately before the `Secure` attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host.
CVE-2026-82209: (needs triaging) When libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a `Set-Cookie` header where the `Domain` attribute explicitly matches an origin host that is itself a public suffix (e.g., `Domain=co.uk` set by `co.uk`). Instead of coercing it into a strict host-only cookie, libcurl saves the cookie with wildcard domain scope (`.co.uk`). Consequently, the cookie is inappropriately included in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix (e.g., `attacker.co.uk`).
CVE-2026-86409: (needs triaging)
CVE-2026-86410: (needs triaging)
CVE-2026-86414: (needs triaging)
CVE-2026-87862: (needs triaging)
CVE-2026-87863: (needs triaging)
CVE-2026-87864: (needs triaging)
CVE-2026-87865: (needs triaging)
CVE-2026-92386: (needs triaging)
CVE-2026-92387: (needs triaging)
CVE-2026-92388: (needs triaging)
CVE-2026-92389: (needs triaging)
CVE-2026-92390: (needs triaging)
CVE-2026-92391: (needs triaging)
CVE-2026-94266: (needs triaging)
CVE-2026-107928: (needs triaging)
CVE-2026-107929: (needs triaging)

You can find information about how to handle these issues in the security team's documentation.

Created: 2026-01-07 Last update: 2026-10-15 05:00

debian/patches: 2 patches to forward upstream low

Among the 5 debian patches available in version 8.23.0-1 of the package, we noticed the following issues:

2 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: 2026-10-14 16:32

testing migrations

This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
excuses:
- Migration status for curl (8.22.0-1 to 8.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Autopkgtest for asterisk/1:22.10.1+dfsg+~cs6.17.60671434-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for curl/8.23.0-1: amd64: Regression ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for debusine/0.16.0: amd64: Pass ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Pass ♻ (reference ♻), ppc64el: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for dracut: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), armhf: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), s390x: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for feh/3.12.2-1: arm64: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻
- ∙ ∙ Autopkgtest for fwupd/2.1.8-1: amd64: Regression ♻ (reference ♻), arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for libqalculate/5.12.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for libreoffice/4:26.8.1.1-3: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Test triggered (failure will be ignored), armhf: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for nginx/1.30.4-7: amd64: Pass ♻, arm64: Pass ♻, i386: Pass ♻ (reference ♻), ppc64el: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for privoxy/4.2.0-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Pass, armhf: Failed (not a regression) ♻ (reference ♻), i386: Reference test triggered, but real test failed already ♻, ppc64el: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for ruby-curb/1.4.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for snac2/2.95-1: ppc64el: Pass ♻
- ∙ ∙ Autopkgtest for spamassassin/4.0.2+svn1938422-1: amd64: Pass ♻, arm64: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻
- ∙ ∙ Autopkgtest for xerces-c/3.2.4+debian-1.3: amd64: Pass ♻, arm64: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻
- ∙ ∙ Missing build on riscv64
- ∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
- ∙ ∙ Lintian check waiting for test results on riscv64 - info
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curl.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- ∙ ∙ 4 days old (needed 2 days)
- Not considered

news

[rss feed]

[2026-10-17] Accepted curl 8.14.1-2+deb13u7 (source) into proposed-updates (Debian FTP Masters) (signed by: Samuel Henrique)
[2026-10-14] Accepted curl 8.14.1-2+deb13u7 (source) into stable-security (Debian FTP Masters) (signed by: Samuel Henrique)
[2026-10-14] Accepted curl 8.23.0-1 (source) into unstable (Samuel Henrique)
[2026-10-08] Accepted curl 8.23.0~rc3-1+exp1 (source) into experimental (Carlos Henrique Lima Melara)
[2026-10-08] Accepted curl 8.23.0~rc3-1 (source) into unstable (Carlos Henrique Lima Melara)
[2026-09-26] Accepted curl 8.23.0~rc2-1+exp1 (source) into experimental (Samuel Henrique)
[2026-09-26] Accepted curl 8.23.0~rc2-1 (source) into unstable (Samuel Henrique)
[2026-09-24] Accepted curl 8.23.0~rc1-2 (source) into unstable (Samuel Henrique)
[2026-09-22] Accepted curl 8.23.0~rc1-1 (source) into unstable (Samuel Henrique)
[2026-09-19] curl 8.22.0-1 MIGRATED to testing (Debian testing watch)
[2026-09-11] Accepted curl 8.22.0-1+exp1 (source) into experimental (Samuel Henrique)
[2026-09-02] Accepted curl 8.22.0-1 (source) into unstable (Samuel Henrique)
[2026-08-27] Accepted curl 8.22.0~rc3-1+exp1 (source) into experimental (Samuel Henrique)
[2026-08-27] Accepted curl 8.22.0~rc3-1 (source) into unstable (Samuel Henrique)
[2026-08-24] Accepted curl 8.22.0~rc2-2 (source) into unstable (Carlos Henrique Lima Melara)
[2026-08-18] Accepted curl 8.22.0~rc2-1 (source) into unstable (Samuel Henrique)
[2026-07-24] Accepted curl 8.21.0-2~bpo13+1 (source) into stable-backports (Samuel Henrique)
[2026-07-24] curl 8.21.0-2 MIGRATED to testing (Debian testing watch)
[2026-07-17] Accepted curl 8.14.1-2+deb13u5 (source) into proposed-updates (Debian FTP Masters) (signed by: Samuel Henrique)
[2026-06-30] Accepted curl 8.14.1-2+deb13u4 (source) into proposed-updates (Debian FTP Masters) (signed by: Samuel Henrique)
[2026-06-30] Accepted curl 7.88.1-10+deb12u15 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Samuel Henrique)
[2026-06-28] Accepted curl 8.21.0-2+exp1 (source) into experimental (Carlos Henrique Lima Melara)
[2026-06-28] Accepted curl 8.21.0-2 (source) into unstable (Carlos Henrique Lima Melara)
[2026-06-26] Accepted curl 8.21.0-1+exp1 (source) into experimental (Carlos Henrique Lima Melara)
[2026-06-25] Accepted curl 8.21.0-1 (source) into unstable (Carlos Henrique Lima Melara)
[2026-06-19] Accepted curl 8.21.0~rc3-1+exp1 (source) into experimental (Carlos Henrique Lima Melara)
[2026-06-19] Accepted curl 8.21.0~rc3-1 (source) into unstable (Carlos Henrique Lima Melara)
[2026-06-14] Accepted curl 8.21.0~rc2-1+exp1 (source) into experimental (Samuel Henrique)
[2026-06-13] Accepted curl 8.21.0~rc2-1 (source) into unstable (Samuel Henrique)
[2026-06-08] Accepted curl 8.20.0-5~bpo13+1 (source amd64 all) into stable-backports (Debian FTP Masters) (signed by: Samuel Henrique)

bugs [bug history graph]

all: 49 53
RC: 0
I&N: 38 40
M&W: 11 13
F&P: 0
patch: 9 10

links

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

ubuntu

[Information about Ubuntu for Debian Developers]

version: 8.20.0-2ubuntu11
81 bugs (3 patches)
patches for 8.20.0-2ubuntu11