You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update 2026-10-25: Dependency-Track 4.14.6 and 5.2.1 are now available, both of which remove the compromised certificates from Java's cacerts. The workarounds outlined in this post are not required for these versions. If you cannot upgrade anytime soon, the workarounds may still be useful to apply.
Multiple distros, languages, and tools have received patches to explicitly denylist the compromised certificates. This is necessary when certificate revocation lists are not consulted.
Dependency-Track's API server is a Java application, and connects to various external sources for data retrieval. Java does not, by default, consult revocation lists. Until a patch is available, you can apply workarounds.
Note
The frontend does not make any outgoing requests and is not impacted by this issue.
Confirmed workarounds
Apply one of the following workarounds. Choose whichever fits your operational constraints best.
Enabling certificate revocation lists
We were able to verify that the -Dcom.sun.net.ssl.checkRevocation=true and -Dcom.sun.security.enableCRLDP=true JVM flags, as documented here, successfully close the gap.
If you deploy Dependency-Track using container images, you can apply this immediately using the EXTRA_JAVA_OPTIONS environment variable:
As identified by Sonatype, this workaround is not complete. Do not rely on it for full mitigation.
The JVM provides a mechanism to block intermediate certificates, by listing their fingerprints in the $JAVA_HOME/lib/security/blocked.certs file. The full procedure is documented here.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Important
Update 2026-10-25: Dependency-Track 4.14.6 and 5.2.1 are now available, both of which remove the compromised certificates from Java's
cacerts. The workarounds outlined in this post are not required for these versions. If you cannot upgrade anytime soon, the workarounds may still be useful to apply.As you may have been made aware of already, the private keys of eMudhra intermediate CA certificates have been compromised. An attacker with the private key of any of the compromised intermediate CAs could impersonate any website or service.
Multiple distros, languages, and tools have received patches to explicitly denylist the compromised certificates. This is necessary when certificate revocation lists are not consulted.
Dependency-Track's API server is a Java application, and connects to various external sources for data retrieval. Java does not, by default, consult revocation lists. Until a patch is available, you can apply workarounds.
Note
The frontend does not make any outgoing requests and is not impacted by this issue.
Confirmed workarounds
Apply one of the following workarounds. Choose whichever fits your operational constraints best.
Enabling certificate revocation lists
We were able to verify that the
-Dcom.sun.net.ssl.checkRevocation=trueand-Dcom.sun.security.enableCRLDP=trueJVM flags, as documented here, successfully close the gap.If you deploy Dependency-Track using container images, you can apply this immediately using the
EXTRA_JAVA_OPTIONSenvironment variable:Recreate the container afterwards to ensure the environment variable takes effect.
If you deploy the JARs manually, simply add those options to your
javacommand, e.g.:Restart the application afterwards.
Using the JVM'sblocked.certsWarning
As identified by Sonatype, this workaround is not complete. Do not rely on it for full mitigation.
The JVM provides a mechanism to block intermediate certificates, by listing their fingerprints in the
$JAVA_HOME/lib/security/blocked.certsfile. The full procedure is documented here.For the lazy, here's a prebuilt file:
blocked.certs
If you deploy Dependency-Track using container images, you can mount this file into the container, e.g.:
Recreate the container afterwards to ensure the file is mounted.
If you deploy the JARs manually, you'll need to add the fingerprints to your JVM's installation. Restart the application afterwards.
All reactions