Summary
google-api-client ships a bundled root certificate store (google.p12) used by GoogleNetHttpTransport.newTrustedTransport() and, before 2.9.0, by GoogleApacheHttpTransport.newTrustedTransport() and GoogleApache5HttpTransport.newTrustedTransport(). In versions before 2.9.2 this store is a 2013 snapshot that trusts Sectigo's AAA Certificate Services, which cross-signed eight eMudhra (emSign) intermediate CAs whose private keys are recoverable from their certificates.
An attacker with one of the recovered keys can issue certificates for any hostname, including *.googleapis.com, and affected clients accept them. An attacker who also has an on-path position can intercept or modify HTTPS traffic, including OAuth 2.0 access tokens.
Version 2.9.2 regenerates the bundled store from https://pki.goog/roots.pem, which does not contain AAA Certificate Services. Upgrade to 2.9.2 or later.
Details
- Before 2.9.0: the
newTrustedTransport() methods above and GoogleUtils.getCertificateTrustStore() configure TLS to trust only the bundled store. JDK and operating-system trust store updates do not reach these clients.
- 2.9.0 and 2.9.1:
getCertificateTrustStore() (PR #2613) loads the JDK cacerts file first and falls back to the bundled store only if that file cannot be opened. In practice this may happen on Android, in GraalVM native images, or when cacerts has a non-default password.
- The Apache transports stopped using the bundled store in 2.9.0.
GoogleApache5HttpTransport ships in the separate artifact com.google.api-client:google-api-client-apache-v5; versions 2.7.0–2.8.1 of that artifact are affected and 2.9.0 or later is not.
- Generated service libraries (
com.google.apis:google-api-services-*): each pins an exact google-api-client version, shown as its version suffix (…-2.0.0 depends on 2.0.0). A build that declares only a service library with a suffix earlier than -2.9.2 resolves an affected google-api-client.
The bundled store never contained the emSign roots; AAA Certificate Services is the only affected root in it. Java does not check certificate revocation by default, so revocation of the intermediates does not mitigate the issue.
Not affected: applications that construct new NetHttpTransport(), new ApacheHttpTransport() or new Apache5HttpTransport() directly — the default in google-auth-library-java and google-cloud-java — and the Apache newTrustedTransport() methods on 2.9.0 or later. These use the JDK trust store, so apply your JDK vendor's security update (and on Windows, the Windows root certificate update).
Patches
com.google.api-client:google-api-client / google-api-client-bom 2.9.2 (release, PR #2636).
com.google.apis:google-api-services-*: upgrade to a release whose version ends in -2.9.2 or later (for example google-api-services-bigquery:v2-rev20260922-2.9.2), or manage google-api-client at 2.9.2 in <dependencyManagement> / Gradle constraints.
com.google.cloud:libraries-bom 26.91.0 or later imports google-api-client-bom 2.9.2.
Workarounds
If you cannot upgrade, stop calling the newTrustedTransport() methods and GoogleUtils.getCertificateTrustStore(); construct the transport directly (new NetHttpTransport() etc.) so TLS uses the JDK trust store, and make sure that store has been updated.
Verification
Check that none of these roots is present in the trust store your application uses (JDK cacerts, OS store, or the bundled store on affected versions):
AAA Certificate Services — SHA-256 D7:A7:A0:FB:5D:7E:27:31:D7:71:E9:48:4E:BC:DE:F7:1D:5F:0C:3E:0A:29:48:78:2B:C8:3E:E0:EA:69:9E:F4
emSign ECC Root CA - G3 — SHA-256 86:A1:EC:BA:08:9C:4A:8D:3B:BE:27:34:C6:12:BA:34:1D:81:3E:04:3C:F9:E8:A8:62:CD:5C:57:A3:6B:BE:6B
emSign Root TLS CA - G3 — SHA-256 7D:D7:8D:5F:4F:13:45:9A:83:DF:F9:AB:BB:A6:2E:DB:AF:6F:2D:10:2B:F2:57:FD:71:2F:4D:9F:27:46:ED:8D
References
Summary
google-api-clientships a bundled root certificate store (google.p12) used byGoogleNetHttpTransport.newTrustedTransport()and, before 2.9.0, byGoogleApacheHttpTransport.newTrustedTransport()andGoogleApache5HttpTransport.newTrustedTransport(). In versions before 2.9.2 this store is a 2013 snapshot that trusts Sectigo'sAAA Certificate Services, which cross-signed eight eMudhra (emSign) intermediate CAs whose private keys are recoverable from their certificates.An attacker with one of the recovered keys can issue certificates for any hostname, including
*.googleapis.com, and affected clients accept them. An attacker who also has an on-path position can intercept or modify HTTPS traffic, including OAuth 2.0 access tokens.Version 2.9.2 regenerates the bundled store from https://pki.goog/roots.pem, which does not contain
AAA Certificate Services. Upgrade to 2.9.2 or later.Details
newTrustedTransport()methods above andGoogleUtils.getCertificateTrustStore()configure TLS to trust only the bundled store. JDK and operating-system trust store updates do not reach these clients.getCertificateTrustStore()(PR #2613) loads the JDKcacertsfile first and falls back to the bundled store only if that file cannot be opened. In practice this may happen on Android, in GraalVM native images, or whencacertshas a non-default password.GoogleApache5HttpTransportships in the separate artifactcom.google.api-client:google-api-client-apache-v5; versions 2.7.0–2.8.1 of that artifact are affected and 2.9.0 or later is not.com.google.apis:google-api-services-*): each pins an exactgoogle-api-clientversion, shown as its version suffix (…-2.0.0depends on 2.0.0). A build that declares only a service library with a suffix earlier than-2.9.2resolves an affectedgoogle-api-client.The bundled store never contained the emSign roots;
AAA Certificate Servicesis the only affected root in it. Java does not check certificate revocation by default, so revocation of the intermediates does not mitigate the issue.Not affected: applications that construct
new NetHttpTransport(),new ApacheHttpTransport()ornew Apache5HttpTransport()directly — the default ingoogle-auth-library-javaandgoogle-cloud-java— and the ApachenewTrustedTransport()methods on 2.9.0 or later. These use the JDK trust store, so apply your JDK vendor's security update (and on Windows, the Windows root certificate update).Patches
com.google.api-client:google-api-client/google-api-client-bom2.9.2 (release, PR #2636).com.google.apis:google-api-services-*: upgrade to a release whose version ends in-2.9.2or later (for examplegoogle-api-services-bigquery:v2-rev20260922-2.9.2), or managegoogle-api-clientat 2.9.2 in<dependencyManagement>/ Gradle constraints.com.google.cloud:libraries-bom26.91.0 or later importsgoogle-api-client-bom2.9.2.Workarounds
If you cannot upgrade, stop calling the
newTrustedTransport()methods andGoogleUtils.getCertificateTrustStore(); construct the transport directly (new NetHttpTransport()etc.) so TLS uses the JDK trust store, and make sure that store has been updated.Verification
Check that none of these roots is present in the trust store your application uses (JDK
cacerts, OS store, or the bundled store on affected versions):AAA Certificate Services— SHA-256D7:A7:A0:FB:5D:7E:27:31:D7:71:E9:48:4E:BC:DE:F7:1D:5F:0C:3E:0A:29:48:78:2B:C8:3E:E0:EA:69:9E:F4emSign ECC Root CA - G3— SHA-25686:A1:EC:BA:08:9C:4A:8D:3B:BE:27:34:C6:12:BA:34:1D:81:3E:04:3C:F9:E8:A8:62:CD:5C:57:A3:6B:BE:6BemSign Root TLS CA - G3— SHA-2567D:D7:8D:5F:4F:13:45:9A:83:DF:F9:AB:BB:A6:2E:DB:AF:6F:2D:10:2B:F2:57:FD:71:2F:4D:9F:27:46:ED:8DReferences