Press release · October 27, 2026 · globenewswire.com
Broadcom Inc. ships 89 TrueSource Spring Enterprise vulnerability fixes
- About Broadcom
- Also names services
- Read the original
Summary
Broadcom Inc. has shipped fixes for 89 newly identified vulnerabilities in TrueSource Spring Enterprise, ahead of public disclosure. The fixes reached customers with early access, and they bring the total number of vulnerabilities fixed across TrueSource offerings to 408.
Patches secure an environment only once they are deployed, which leaves a gap between release and installation. TrueSource Spring Enterprise now includes TrueSource Hub, intended to help organizations assess application exposure, prioritize critical fixes, and track status.
TrueSource Hub connects to an organization’s code repositories and displays the security status of open source components used by each application, including Java, Python, and JavaScript libraries, container images, and data services. It tracks patch status in a live view. Build plugins for Application Advisor fit into existing Maven and Gradle workflows and generate pull requests that carry approved fixes into merging.
Broadcom engineers fixed 406 new vulnerabilities in 2026, delivered more than 1,090 fixes including 798 backports, reviewed over 2,600 reports, and filtered out more than 3,000 false alarms. Each fix is delivered simultaneously across all supported versions, and current versions receive security-only patches. TrueSource Spring Enterprise, including Hub and build plugins, is generally available, and fixes are accessible immediately to early-access customers.
“Security isn’t a one-time initiative; it’s an ongoing commitment. In June, we pledged to identify and resolve Spring vulnerabilities faster than ever, and today’s release demonstrates our continued momentum,” said Purnima Padmanabhan, general manager, Tanzu Division, Broadcom.
“Our customers receive critical fixes early in a deployable format, with complete visibility into where patches belong and confirmation when they land. Crucially, fixes are contributed back to the open source community—because open source remains resilient only when businesses actively invest in ecosystem health.” Padmanabhan said. Detailed vulnerability information will be published once fixes reach the community and CVEs are issued.
Our summary. The original keeps its own byline.