SBOM security assessment: Vulnerabilities affecting third-party components

This section contains time sensitive announcements about specific cyber threats, vulnerabilities and scams. Each alert has information you need to be aware of, and what actions to take to mitigate any risk to you or your organisation.

Subscribe to our updates to be notified as soon as we publish an alert.

10:40AM, 16 November 2026

TLP Rating: Clear

SBOM security assessment: Vulnerabilities affecting third-party components

Multiple vulnerabilities have been discovered in a series of Java-based projects, some of which could allow an attacker to bypass authentication, read arbitrary files or access sensitive information. Please note that the vulnerabilities affect components in older versions of projects which may have been changed, updated or deleted since.

Organisations should assess potentially affected systems and apply vendor-provided patches as soon as possible. 

What's happening

Systems affected

  • Apache Kerby: Allows an attacker to impersonate any user, including administrators, by obtaining valid Kerberos authentication tickets. Affected Versions: Apache Kerby 1.0.0 to 2.0.x (fixed in 2.1.0)
  • MockServer: Allows unauthenticated attackers to read files and access internal systems through XML processing and server-side request forgery (SSRF). Affected Versions: MockServer 5.5.4 and later; partial fix introduced in 6.0.0
  • Javassist: An exposed Javassist Webserver can allow attackers to read arbitrary files from the underlying host system. Affected Versions: Javassist 3.13.0-GA to 3.31.x (fixed in 3.32.0-GA)
  • SAAJ (SOAP Parser): Malicious SOAP messages may allow file disclosure, internal network access, or denial-of-service in specific configurations. Affected Versions: All versions prior to 3.0.0
  • JJWT Signature Validation Bypass: Under certain implementation conditions, applications may accept forged JWT authentication tokens without validating the signature. Affected Versions: All versions prior to 0.12.0
  • WireMock Arbitrary File Delete: An unauthenticated attacker may be able to delete files on Windows systems running exposed WireMock instances. Affected Versions: WireMock 2.14.0 to 2.x (fixed in 3.0.0-beta-1)
  • JJWT Denial of Service: Specially crafted JWTs can exhaust memory and cause application outages. Affected Versions: JJWT 0.6.0 to 0.11.x (fixed in 0.12.0)
  • Google libphonenumber: Malicious input can consume excessive CPU resources and potentially disrupt application availability. Affected Versions: libphonenumber 3.1 to 9.0.35 (fixed in 9.0.36)
  • Javassist Resource Exhaustion: Repeated malformed requests can exhaust system resources and cause service disruption. Affected Versions: Javassist 3.13.0-GA to 3.31.x (fixed in 3.32.0-GA)
  • WireMock Path Traversal: An attacker may gain limited access to files outside WireMock's intended storage directory. Affected Versions: WireMock 2.16.0 to 2.x (fixed in 3.0.0-beta-1) 
  • Auth0 Java JWT: Malformed authentication tokens can trigger application exceptions and potentially impact service availability. Affected Versions: java-jwt 3.0.1 to 3.19.1 (fixed in 3.19.2)
  • Apache Qpid Broker-J: Authentication timing differences could theoretically assist password recovery, although exploitation is difficult in practice. Affected Versions: Qpid Broker-J 0.26 to 9.x (fixed in 10.0.0)

What to do

Prevention

Upgrade to a supported, non-vulnerable version where available, or remove the affected component if no fixed version exists.

More information

Identify potentially affected products within your environment and refer to the guidance provided by the maintainers of each codebase for remediation requirements.