Skip to content

Current latest container version still has compromised eMudhra CA certificates #2707

Closed

Description

@OscarVanL

Bug Description

The current latest gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.26.2 is vulnerable to MITM attacks as the eMudhra CA store is still included in the latest version of the container.

Specifically, the service still has an outdated Debian CA store with both affected trust roots. Additionally, the service binary was built with Go 1.27.2, which doesn't contain the revocation list that was added in Go 1.27.3.

Example code (or command)

How to prove both statements (built with go 1.27.2 and still contains revoked CAs):

Built on go 1.27.2:

# 1. Create (don't run) a container from the amd64 variant and copy the two files out
> docker create --platform linux/amd64 --name csp-check gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.26.2
> docker cp csp-check:/cloud-sql-proxy ./cloud-sql-proxy
> docker cp csp-check:/etc/ssl/certs/ca-certificates.crt ./ca-certificates.crt
> docker rm csp-check

# 2. Prove the Go toolchain it was built with
> go version cloud-sql-proxy
cloud-sql-proxy: go1.27.2

Contains distrusted CAs:

> python3 -c "
import hashlib, re, ssl
bad = {'86a1ecba089c4a8d3bbe2734c612ba341d813e043cf9e8a862cd5c57a36bbe6b': 'emSign ECC Root CA - G3', 'd7a7a0fb5d7e2731d771e9484ebcdef71d5f0c3e0a2948782bc83ee0ea699ef4': 'AAA Certificate Services'}
pems = re.findall(r'-----BEGIN CERTIFICATE-----.+?-----END CERTIFICATE-----', open('ca-certificates.crt').read(), re.S)
print(len(pems), [bad[h] for p in pems if (h := hashlib.sha256(ssl.PEM_cert_to_DER_cert(p)).hexdigest()) in bad])

150 ['AAA Certificate Services', 'emSign ECC Root CA - G3']

Stacktrace

Steps to reproduce?

See above

Environment

  1. OS type and version: N/A
  2. Cloud SQL Proxy version (./cloud-sql-proxy --version): 2.26.2
  3. Proxy invocation command (for example, ./cloud-sql-proxy --port 5432 INSTANCE_CONNECTION_NAME): N/A

Additional Details

No response

Activity

  1. added
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    on Oct 22, 2026
  2. changed the title [-]Current latest container version still has comromised eMudhra CA certificates[/-] [+]Current latest container version still has compromised eMudhra CA certificates[/+] on Oct 22, 2026
  3. enocom commented on Oct 22, 2026

    @enocom
    Member

    Thanks for flagging this, @OscarVanL. We'll be getting a release out ASAP.

  4. added
    priority: p0Highest priority. Critical issue. P0 implies highest priority.
    on Oct 22, 2026
  5. self-assigned this
    on Oct 22, 2026
  6. pinned this issue on Oct 22, 2026
  7. unpinned this issue on Oct 22, 2026
  8. assigned and unassigned on Oct 22, 2026
  9. added a commit that references this issue on Oct 22, 2026
    e58f8fb
  10. reopened this on Oct 22, 2026
  11. kgala2 commented on Oct 22, 2026

    @kgala2
    Contributor

    The container image has been updated and Auth Proxy v2.26.3 should be available to use now https://github.com/GoogleCloudPlatform/cloud-sql-proxy/releases/tag/v2.26.3

  12. OscarVanL commented on Oct 23, 2026

    @OscarVanL
    Author

    Thank you!

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

Metadata

Metadata

Assignees

Labels

priority: p0Highest priority. Critical issue. P0 implies highest priority.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    ⌂ 换网址