Skip to content

Fixable CVEs in smallstep/step-ca (5 critical, 94 high) #1003

Open

Description

@github-actions

The weekly CVE scan found fixable HIGH or CRITICAL vulnerabilities in smallstep/step-ca. This body is rewritten by every scan, and the issue closes itself when a scan finds the pinned digest clean.

The fix is normally the Dependabot bump for this image. If upstream has not released one, the fixed versions below say what to wait for.

smallstep/step-ca:0.30.2

Stacks: sensitive. Digest: sha256:a2b17872915c193259b75a5474c398326f41bd199f0842093e52cf4182bc8270.

Severity ID Package Installed Fixed in
CRITICAL CVE-2026-111497 brotli-libs 1.2.0-r0 1.2.1-r0
CRITICAL CVE-2026-33815 github.com/jackc/pgx/v5 v5.8.0 5.9.0
CRITICAL CVE-2026-33816 github.com/jackc/pgx/v5 v5.8.0 5.9.0
CRITICAL CVE-2026-31789 libcrypto3 3.5.5-r0 3.5.6-r0
CRITICAL CVE-2026-31789 libssl3 3.5.5-r0 3.5.6-r0
HIGH CVE-2026-33630 c-ares 1.34.6-r0 1.34.8-r0
HIGH CVE-2026-11352 curl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-11586 curl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-12064 curl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-5773 curl 8.17.0-r1 8.20.0-r0
HIGH CVE-2026-6276 curl 8.17.0-r1 8.20.0-r0
HIGH CVE-2026-8286 curl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-8458 curl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-8925 curl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-8927 curl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-92392 curl 8.17.0-r1 8.23.0-r0
HIGH CVE-2026-9547 curl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-34986 github.com/go-jose/go-jose/v3 v3.0.4 3.0.5
HIGH CVE-2026-116587 github.com/go-jose/go-jose/v4 v4.1.3 4.1.6
HIGH CVE-2026-34986 github.com/go-jose/go-jose/v4 v4.1.3 4.1.4
HIGH CVE-2026-63209 github.com/klauspost/compress v1.18.0 1.18.7
HIGH CVE-2026-29181 go.opentelemetry.io/otel v1.39.0 1.41.0
HIGH CVE-2026-39828 golang.org/x/crypto v0.49.0 0.52.0
HIGH CVE-2026-39829 golang.org/x/crypto v0.49.0 0.52.0
HIGH CVE-2026-39830 golang.org/x/crypto v0.49.0 0.52.0
HIGH CVE-2026-39831 golang.org/x/crypto v0.49.0 0.52.0
HIGH CVE-2026-39832 golang.org/x/crypto v0.49.0 0.52.0
HIGH CVE-2026-39835 golang.org/x/crypto v0.49.0 0.52.0
HIGH CVE-2026-42508 golang.org/x/crypto v0.49.0 0.52.0
HIGH CVE-2026-46595 golang.org/x/crypto v0.49.0 0.52.0
HIGH CVE-2026-46597 golang.org/x/crypto v0.49.0 0.52.0
HIGH CVE-2026-56854 golang.org/x/crypto v0.49.0 0.55.0
HIGH CVE-2026-25681 golang.org/x/net v0.52.0 0.55.0
HIGH CVE-2026-27136 golang.org/x/net v0.52.0 0.55.0
HIGH CVE-2026-33814 golang.org/x/net v0.52.0 0.53.0
HIGH CVE-2026-39821 golang.org/x/net v0.52.0 0.55.0
HIGH CVE-2026-46600 golang.org/x/net v0.52.0 0.56.0
HIGH CVE-2026-78661 golang.org/x/net v0.52.0 0.62.0
HIGH CVE-2026-78669 golang.org/x/net v0.52.0 0.60.0
HIGH CVE-2026-56851 golang.org/x/text v0.35.0 0.41.0
HIGH CVE-2026-56852 golang.org/x/text v0.35.0 0.39.0
HIGH CVE-2026-84304 google.golang.org/grpc v1.79.3 1.83.1
HIGH CVE-2026-84445 google.golang.org/grpc v1.79.3 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e
HIGH GHSA-hrxh-6v49-42gf google.golang.org/grpc v1.79.3 1.82.1
HIGH CVE-2026-32316 jq 1.8.1-r0 1.8.2-r0
HIGH CVE-2026-40164 jq 1.8.1-r0 1.8.2-r0
HIGH CVE-2026-14456 libcrypto3 3.5.5-r0 3.5.8-r0
HIGH CVE-2026-28387 libcrypto3 3.5.5-r0 3.5.6-r0
HIGH CVE-2026-28388 libcrypto3 3.5.5-r0 3.5.6-r0
HIGH CVE-2026-28389 libcrypto3 3.5.5-r0 3.5.6-r0
HIGH CVE-2026-28390 libcrypto3 3.5.5-r0 3.5.6-r0
HIGH CVE-2026-45447 libcrypto3 3.5.5-r0 3.5.7-r0
HIGH CVE-2026-11352 libcurl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-11586 libcurl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-12064 libcurl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-5773 libcurl 8.17.0-r1 8.20.0-r0
HIGH CVE-2026-6276 libcurl 8.17.0-r1 8.20.0-r0
HIGH CVE-2026-8286 libcurl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-8458 libcurl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-8925 libcurl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-8927 libcurl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-92392 libcurl 8.17.0-r1 8.23.0-r0
HIGH CVE-2026-9547 libcurl 8.17.0-r1 8.22.0-r0
HIGH CVE-2026-14456 libssl3 3.5.5-r0 3.5.8-r0
HIGH CVE-2026-28387 libssl3 3.5.5-r0 3.5.6-r0
HIGH CVE-2026-28388 libssl3 3.5.5-r0 3.5.6-r0
HIGH CVE-2026-28389 libssl3 3.5.5-r0 3.5.6-r0
HIGH CVE-2026-28390 libssl3 3.5.5-r0 3.5.6-r0
HIGH CVE-2026-45447 libssl3 3.5.5-r0 3.5.7-r0
HIGH CVE-2026-107891 musl 1.2.5-r21 1.2.5-r24
HIGH CVE-2026-40200 musl 1.2.5-r21 1.2.5-r23
HIGH CVE-2026-107891 musl-utils 1.2.5-r21 1.2.5-r24
HIGH CVE-2026-40200 musl-utils 1.2.5-r21 1.2.5-r23
HIGH CVE-2026-27135 nghttp2-libs 1.68.0-r0 1.68.1
HIGH CVE-2026-111943 stdlib v1.26.1 1.26.10, 1.27.3
HIGH CVE-2026-27145 stdlib v1.26.1 1.25.11, 1.26.4
HIGH CVE-2026-32280 stdlib v1.26.1 1.25.9, 1.26.2
HIGH CVE-2026-32281 stdlib v1.26.1 1.25.9, 1.26.2
HIGH CVE-2026-32283 stdlib v1.26.1 1.25.9, 1.26.2
HIGH CVE-2026-33810 stdlib v1.26.1 1.26.2
HIGH CVE-2026-33811 stdlib v1.26.1 1.25.10, 1.26.3
HIGH CVE-2026-33814 stdlib v1.26.1 1.25.10, 1.26.3
HIGH CVE-2026-33818 stdlib v1.26.1 1.25.13, 1.26.6, 1.27.0-rc.3
HIGH CVE-2026-39820 stdlib v1.26.1 1.25.10, 1.26.3
HIGH CVE-2026-39821 stdlib v1.26.1 1.25.13, 1.26.6, 1.27.0-rc.3
HIGH CVE-2026-39822 stdlib v1.26.1 1.25.12, 1.26.5, 1.27.0-rc.2
HIGH CVE-2026-39836 stdlib v1.26.1 1.25.10, 1.26.3
HIGH CVE-2026-42499 stdlib v1.26.1 1.25.10, 1.26.3
HIGH CVE-2026-42504 stdlib v1.26.1 1.25.11, 1.26.4
HIGH CVE-2026-46600 stdlib v1.26.1 1.26.6, 1.27.0-rc.3
HIGH CVE-2026-56853 stdlib v1.26.1 1.25.13, 1.26.6, 1.27.0-rc.3
HIGH CVE-2026-56858 stdlib v1.26.1 1.25.13, 1.26.6, 1.27.0-rc.3
HIGH CVE-2026-56859 stdlib v1.26.1 1.25.13, 1.26.6, 1.27.0-rc.3
HIGH CVE-2026-56860 stdlib v1.26.1 1.25.13, 1.26.6, 1.27.0-rc.3
HIGH CVE-2026-56862 stdlib v1.26.1 1.25.13, 1.26.6, 1.27.0-rc.3
HIGH CVE-2026-78667 stdlib v1.26.1 1.26.9, 1.27.2
HIGH CVE-2026-78669 stdlib v1.26.1 1.26.9, 1.27.2
HIGH CVE-2026-97031 stdlib v1.26.1 1.26.9, 1.27.2
HIGH CVE-2026-85091 zlib 1.3.2-r0 1.3.2-r1

Written by .github/workflows/cve-scan.yml in this run.

Activity

  1. added
    securityA credential, an exposure, or a control that is weaker than recorded
    sensitivestacks/sensitive on trinity (VLAN 99)
    on Oct 7, 2026
  2. changed the title [-]Fixable CVEs in smallstep/step-ca (4 critical, 80 high)[/-] [+]Fixable CVEs in smallstep/step-ca (4 critical, 84 high)[/+] on Oct 10, 2026
  3. github-actions commented on Oct 10, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-78667, CVE-2026-78669, CVE-2026-97031.

  4. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Triage, 2026-10-10: unlike its siblings, this one is stalled upstream, not just waiting on a bump. Nothing in the repo changes yet, and there's a decision to make below.

    Upstream state. 0.30.2 (2026-03-23) is still step-ca's latest release, and Docker Hub has no newer build: every tag was last pushed 2026-03-23. master has moved: its go.mod carries pgx v5.9.2, go-jose v3.0.5/v4.1.4, x/crypto v0.57.0, x/net v0.58.0, grpc v1.84.0 and otel v1.45.0, which clears every Go-module row here. Nobody has cut a release from it. smallstep/certificates#2730 ("Bump vulnerable x/crypto and x/net in v0.30.2", opened 2026-07-02) is still open with no maintainer reply, and smallstep/certificates#2500 complains about the same release cadence. Dependabot has nothing to bump to.

    What the findings are (trivy 0.75.0 against the pinned digest; the same findings appear in step-ca, step and step-kms-plugin):

    Finding Reachable here?
    CRITICAL pgx/v5 v5.8.0 (CVE-2026-33815, -33816) No. scripts/tier-ca.sh runs step ca init --deployment-type standalone with no --db, so the CA uses the default BadgerDB, and the Postgres driver is linked but never opened.
    CRITICAL libssl3/libcrypto3 3.5.5 (CVE-2026-31789) No. It's a 32-bit-only heap overflow, trinity is amd64, and step-ca is a Go binary that does its TLS in Go, not through OpenSSL.
    curl, libcurl, jq, c-ares, nghttp2, musl (Alpine 3.23.3 userland) No. None of them is on step-ca's request path. The healthcheck is step ca health (Go), not curl.
    Go stdlib 1.26.1, ~23 CVEs Yes, partly. The ones that matter are in crypto/tls, crypto/x509, net/http, HTTP/2 and encoding/asn1, all on the TLS listener at :9000. Almost all of them are DoS. The one validation issue, CVE-2026-33810 (x509 DNS name-constraint bypass), would need a chain with name constraints, and this CA's root has none. The net/mail, mime, html/template, encoding/xml and os.Root items aren't reachable from ACME/JWK.
    x/crypto, x/net, grpc, go-jose, otel Low. Mostly DoS. go-jose does parse JWS on the ACME path, but only from a client that reaches :9000.

    Exposure. :9000 is exposed, not published. The only client is Caddy on the sensitive stack's network. The container runs as uid 1000 with a read-only root, every capability dropped except the one needed to exec the binary, and a 256m memory cap. So realistically the risk is a peer on that network knocking the CA over, and Caddy only renews weekly with lifetimes that have plenty of slack (ADR-0037 §3). An outage is noticed, not silent.

    The decision. Waiting is defensible on exposure. But unlike the other open scans, there's no release in sight, and this is the tier's CA. Options, in rising cost:

    1. Wait and leave this open. The scan keeps listing new stdlib CVEs every week until upstream ships.
    2. Add our voice upstream on Bump vulnerable golang.org/x/crypto (v0.49.0) and golang.org/x/net (v0.52.0) in v0.30.2 smallstep/certificates#2730, asking for a 0.30.3 from master.
    3. Build our own image from a pinned master commit with a current Go toolchain, on current Alpine. That clears everything, but it means owning a build of the tier's CA, which no other service on the tier does.

    I'm leaving the choice open. Nothing has been posted upstream.

  5. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Option 2 taken, 2026-10-10: asked upstream for a 0.30.3 (or a rebuild of 0.30.2 on current Go and Alpine) in smallstep/certificates#2730 (comment). Waiting on that, and options 1 and 3 still stand if it goes unanswered.

  6. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    This is waiting on upstream. Nothing in the repo needs to change.

    • The pinned digest is current: smallstep/step-ca:0.30.2 (sha256:a2b17872…). pin-digests.sh reports no drift, so the tag hasn't been rebuilt since it was pinned.
    • There is no newer release on the registry to move to.
    • The fixed versions exist (table above), but no published image includes them yet. Mostly:
      • stdlib: 23 findings, fixed in 8 different versions (see the table)
      • curl: 10 findings, fixed in 2 different versions (see the table)
      • golang.org/x/crypto: 10 findings, fixed in 2 different versions (see the table)
      • libcurl: 10 findings, fixed in 2 different versions (see the table)
      • libcrypto3: 7 findings, fixed in 3 different versions (see the table)
      • libssl3: 7 findings, fixed in 3 different versions (see the table)
      • and 21 more across 12 other packages

    When upstream rebuilds or ships a release with these fixes, Dependabot should open the bump. Check it with trivy and check_image_pins.py, then deploy. The next scan will then close this issue.

  7. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    The criticals, traced against the live CA, 2026-10-10

    This is the same trace as on #979, #1009, #1010 and #1011. It firms up the triage above, which inferred the database type from scripts/tier-ca.sh; this time it's read from the running container (sensitive-step-ca on trinity, smallstep/step-ca:0.30.2@sha256:a2b17872…). The 6 critical rows are 3 CVEs, and none is reachable.

    CVE Package (where) What the bug needs What the live CA does Reachable?
    CVE-2026-33815, CVE-2026-33816 pgx/v5 v5.8.0 (step-ca, step) A connection to a malicious PostgreSQL server. The advisories (GHSA-xgrm-4fwx-7qm8, GHSA-9jj7-4m8r-rfcm) only say "memory-safety". pgx's 5.9.0 changelog describes the fixes as "potential DoS due to panic or OOM if connected to a malicious server that sends deliberately malformed messages". The live ca.json has "db": {"type": "badgerv2", "dataSource": "/home/step/db"}, and /home/step/db holds Badger files (MANIFEST, *.sst, *.vlog). No Postgres DSN is configured, so pgx is linked but never opens a connection. No
    CVE-2026-31789 libssl3/libcrypto3 3.5.5 (Alpine 3.23.3) 32-bit OpenSSL hex-printing an X.509 SKID/AKID large enough to overflow len × 3 The container is x86_64. step-ca and step are static Go binaries (ldd: "Not a valid dynamic program"), so they never load the image's OpenSSL. The CA's TLS and X.509 parsing is Go's crypto/tls/crypto/x509. No

    Confirmed along the way: the live provisioners are JWK and ACME only, and the TLS config is TLS 1.2 to 1.3 with two ECDHE-ECDSA suites, no renegotiation. That matches the triage's assumptions.

    This doesn't change the decision above. Its "yes, partly" row, the Go 1.26.1 stdlib HIGHs in crypto/tls, crypto/x509 and net/http on :9000, is still the real exposure, and it's what the ask on smallstep/certificates#2730 is for. The criticals were never the reason to act.

    What would change this: moving the CA's database to Postgres or MySQL ("db": {"type": "postgresql", …}), or running the image on a 32-bit host.

    To reproduce:

    docker exec sensitive-step-ca cat /home/step/config/ca.json | python3 -c 'import json,sys; c=json.load(sys.stdin); print(c["db"], [p["type"] for p in c["authority"]["provisioners"]])'
    docker exec sensitive-step-ca sh -c 'uname -m; ldd /usr/local/bin/step-ca; ls /home/step/db'

    🤖 Traced by Claude Code

  8. changed the title [-]Fixable CVEs in smallstep/step-ca (4 critical, 84 high)[/-] [+]Fixable CVEs in smallstep/step-ca (4 critical, 85 high)[/+] on Oct 19, 2026
  9. github-actions commented on Oct 19, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-56851.

  10. changed the title [-]Fixable CVEs in smallstep/step-ca (4 critical, 85 high)[/-] [+]Fixable CVEs in smallstep/step-ca (4 critical, 90 high)[/+] on Oct 26, 2026
  11. github-actions commented on Oct 26, 2026

    @github-actions
    Author
  12. changed the title [-]Fixable CVEs in smallstep/step-ca (4 critical, 90 high)[/-] [+]Fixable CVEs in smallstep/step-ca (5 critical, 90 high)[/+] on Nov 2, 2026
  13. github-actions commented on Nov 2, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-116587.

  14. changed the title [-]Fixable CVEs in smallstep/step-ca (5 critical, 90 high)[/-] [+]Fixable CVEs in smallstep/step-ca (5 critical, 94 high)[/+] on Nov 9, 2026
  15. github-actions commented on Nov 9, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-107891, CVE-2026-78661, CVE-2026-85091.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    securityA credential, an exposure, or a control that is weaker than recordedsensitivestacks/sensitive on trinity (VLAN 99)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions