Security Advisory: SonarQube Action for eMudhra

Hi Anders, we have checked sonarqube-enterprise-2026.5.4.134003.zip (published 2 Nov): the bundled scanner JREs in `jres/` (`OpenJDK21U-jre_*_hotspot_21.0.13_9`) no longer contain emSign ECC Root CA - G3, so that part looks fixed.

However, `lib/sonar-application-2026.5.4.134003.jar` still embeds 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`) in `com/google/api/client/googleapis/google.p12` and `google.jks`, same as 2026.5.3.

Have you now verified that no SonarQube code path loads this store through `GoogleUtils.getCertificateTrustStore()` / `newTrustedTransport()`?

Hey @Praveen_A_Nair, I haven’t gotten any news about it. I will be looping in someone who may be able to answer.

Hi @Praveen_A_Nair, I found out more about this. SonarQube isn’t exposed through that trust store, because nothing ever loads it. As you suggest, we never run any of the library’s code paths which loads the trust store. SonarQube’s connections to Google use standard HTTP transports which rely on the JVM’s default trust store.

So if you have removed AAA Certificate Services from the cacerts of the Java runtime running SonarQube (or if you’re on the patched Docker image), no SonarQube connection trusts it. The copy inside the jar is unused, and will be removed in an upcoming dependency update.

Hi all,

Release posts have been published to Community:

1 Like