Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

tribulant

About This Vendor

tribulant is a technology vendor producing software and infrastructure products. As a software provider, tribulant's broad product portfolio across multiple domains—including operating systems, cloud infrastructure, enterprise applications, databases, networking, and security tools—creates a large attack surface. Additionally, long support cycles, widespread deployment, and continuous feature development contribute to the accumulation of discovered vulnerabilities over time. Major vendors typically report higher CVE counts not necessarily due to inferior security, but because of greater exposure to security research, responsible disclosure practices, and the sheer complexity of maintaining multiple product lines and legacy systems. Regular security assessments and patching of tribulant's products are critical for organizations running their software in production environments.

Vulnerability Trends for This Vendor

SecUtils has indexed 24 known vulnerabilities from tribulant. This includes 2 critical-severity issues and 7 high-severity issues that represent significant risk. These vulnerabilities affect 5 distinct products across tribulant's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2014 through 2026, indicating decades of continuous security attention and research. Organizations deploying tribulant products should maintain active vulnerability monitoring, prioritize critical patches, and implement compensating controls where patches cannot be applied immediately.

ID Date Published Last Modified Severity (CVSSv3) Severity (CVSSv2) Exploit Available
CVE-2014-5460 2014-09-11 2026-06-17 - 6.5 Likely
CVE-2018-17946 2018-10-03 2026-06-17 6.1 4.3 Likely
CVE-2018-18017 2019-04-15 2026-06-17 6.1 4.3 Likely
CVE-2018-18018 2019-04-15 2026-06-17 9.8 7.5 Likely
CVE-2018-18019 2019-04-15 2026-06-17 6.1 4.3 Likely
CVE-2019-14787 2019-08-09 2026-06-17 5.4 3.5 Unknown
CVE-2019-14788 2019-08-15 2026-06-17 8.8 6.5 Likely
CVE-2018-20987 2019-08-22 2026-06-17 9.8 7.5 Likely
CVE-2019-15828 2019-08-30 2026-06-17 8.8 6.8 Likely
CVE-2020-35932 2021-01-01 2026-06-17 7.5 6.0 Unknown
CVE-2021-24882 2021-11-23 2026-06-17 4.8 3.5 Unknown
CVE-2023-30478 2023-11-10 2026-06-17 5.4 - -
CVE-2023-28497 2023-11-12 2026-06-17 5.4 - -
CVE-2023-28491 2023-12-20 2026-06-17 6.7 - -
CVE-2023-4797 2024-01-16 2026-06-17 7.2 - -
CVE-2024-31353 2024-04-10 2026-06-17 5.3 - -
CVE-2024-35718 2024-06-08 2026-06-17 7.1 - -
CVE-2024-37227 2024-06-21 2026-06-17 4.3 - -
CVE-2024-8247 2024-09-06 2026-06-17 8.8 - -
CVE-2024-10181 2024-10-29 2026-06-17 6.4 - -
CVE-2024-13739 2025-03-22 2026-06-17 6.1 - -
CVE-2025-4857 2025-05-31 2026-06-17 7.2 - -
CVE-2026-17520 2026-08-29 2026-08-31 4.8 - -
CVE-2026-17522 2026-08-29 2026-08-31 5.4 - -

How SecUtils Normalizes Vendor Data

SecUtils aggregates National Vulnerability Database (NVD) and MITRE records for tribulant by normalizing vendor identifiers across diverse data sources, mapping vendor names to their associated product lines, and collecting all known vulnerabilities under a unified vendor context. For every CVE associated with tribulant's products, we extract and structure Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) categories, CVSS severity metrics, and reference links to enable rapid vulnerability identification and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and vendor vulnerability tracking.