Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

autonomy

About This Vendor

autonomy is a technology vendor producing software and infrastructure products. As a software provider, autonomy'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 autonomy's products are critical for organizations running their software in production environments.

Vulnerability Trends for This Vendor

SecUtils has indexed 25 known vulnerabilities from autonomy. This includes 24 high-severity issues requiring prompt remediation. These vulnerabilities affect 16 distinct products across autonomy's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2005 through 2013, reflecting sustained security scrutiny over multiple years. Organizations deploying autonomy 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-2005-2618 2005-12-31 2025-04-03 - 9.3 Likely
CVE-2005-2619 2005-12-31 2025-04-03 - 9.3 Likely
CVE-2007-5909 2007-11-10 2025-04-09 - 9.3 Likely
CVE-2007-5910 2007-11-10 2025-04-09 - 9.3 Likely
CVE-2007-6008 2007-11-15 2025-04-09 - 9.3 Likely
CVE-2007-5399 2008-04-10 2025-04-09 - 9.3 Likely
CVE-2007-5405 2008-04-10 2025-04-09 - 9.3 Likely
CVE-2007-5406 2008-04-10 2025-04-09 - 9.3 Likely
CVE-2007-6020 2008-04-10 2025-04-09 - 9.3 Likely
CVE-2008-0066 2008-04-10 2025-04-09 - 9.3 Likely
CVE-2008-1101 2008-04-10 2025-04-09 - 9.3 Likely
CVE-2008-1718 2008-04-10 2025-04-09 - 9.3 Likely
CVE-2009-0347 2009-01-29 2025-04-09 - 5.8 Likely
CVE-2008-4564 2009-03-18 2025-04-09 - 9.3 Likely
CVE-2009-3037 2009-09-01 2025-04-09 - 9.3 Likely
CVE-2010-0126 2010-08-17 2025-04-11 - 9.3 Likely
CVE-2010-0131 2010-08-17 2025-04-11 - 9.3 Likely
CVE-2010-0133 2010-08-17 2025-04-11 - 9.3 Likely
CVE-2010-0134 2010-08-17 2025-04-11 - 9.3 Likely
CVE-2010-0135 2010-08-17 2025-04-11 - 9.3 Likely
CVE-2010-1524 2010-08-17 2025-04-11 - 9.3 Likely
CVE-2010-1525 2010-08-17 2025-04-11 - 9.3 Likely
CVE-2011-1218 2011-05-31 2025-04-11 - 9.3 Likely
CVE-2011-1512 2011-05-31 2025-04-11 - 9.3 Likely
CVE-2012-6349 2013-07-18 2025-04-11 - 9.3 Likely

How SecUtils Normalizes Vendor Data

SecUtils aggregates National Vulnerability Database (NVD) and MITRE records for autonomy 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 autonomy'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.