[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fAMGFPo-m9l-6bHrSAv6hivCofJEV5RcoODf3CHsQgBI":3},{"product":4,"cycleMajor":14,"releases":15,"cves":33,"nextMajor":42,"indexable":43},{"id":5,"slug":6,"name":7,"category":8,"vendor":9,"description":10,"logo_url":11,"official_url":9,"synced_at":12,"created_at":13},"631d2164-d631-4ae7-8e0b-cbf66b8f6295","opensuse","Opensuse","os",null,"Developers rely on Opensuse, an operating system that has been around since 2005, to power their applications and systems, and it is maintained by the openSUSE Project community. The community-driven approach ensures that the operating system is shaped by the needs of its users, making it a popular choice among developers who value flexibility and customization. By tracking the end-of-life dates of Opensuse, developers can plan their upgrades and ensure that their systems remain secure and supported. This is particularly important in today's fast-paced technology landscape, where staying ahead of potential security vulnerabilities is crucial.\n\nThe end-of-life landscape for Opensuse is characterized by a large number of versions that have already reached their end-of-life, with 20 out of 21 versions no longer supported. The next version to expire is 16.0, which will reach its end-of-life on October 31, 2027. This gives developers a clear timeline to plan their upgrades and migrations to newer versions. The most recent version to reach its end-of-life was 15.6, which expired on April 30, 2026. With only one active version currently available, developers should be aware of the upcoming end-of-life dates to avoid any potential disruptions to their systems.\n\nGiven the current security landscape, Opensuse has a clean slate with no tracked CVEs, which is a testament to the community's efforts to maintain a secure operating system. As a result, there are no critical CVEs to report, and no version is particularly affected. Furthermore, with no known vulnerabilities, the KEV status is not applicable. Despite this positive security picture, developers should still prioritize staying up-to-date with the latest versions and security patches to ensure the continued security and integrity of their systems. By doing so, they can take proactive measures to protect their applications and data from potential threats.","https:\u002F\u002Fcdn.simpleicons.org\u002Fopensuse","2026-10-07T02:00:12.129+00:00","2026-05-30T16:23:55.904463+00:00","12",[16,23,28],{"id":17,"product_id":5,"cycle":18,"release_date":19,"eol":20,"eol_boolean":9,"latest":9,"latest_release_date":9,"lts":21,"support":9,"created_at":22},"d8abf9fd-57d8-4e96-8fa7-a5daf8aa95c5","12.3","2013-03-13","2015-01-29",false,"2026-05-30T16:26:03.501267+00:00",{"id":24,"product_id":5,"cycle":25,"release_date":26,"eol":27,"eol_boolean":9,"latest":9,"latest_release_date":9,"lts":21,"support":9,"created_at":22},"9def3578-24cb-43a5-9505-483743ed5b43","12.2","2012-09-05","2014-01-15",{"id":29,"product_id":5,"cycle":30,"release_date":31,"eol":32,"eol_boolean":9,"latest":9,"latest_release_date":9,"lts":21,"support":9,"created_at":22},"3d9306f5-af71-4645-8e4d-1b4f5a37232c","12.1","2011-11-16","2013-05-15",[34],{"cveId":35,"releaseId":17,"cycle":18,"description":36,"severity":37,"cvssScore":38,"epssScore":39,"inKev":21,"publishedAt":40,"url":41},"CVE-2014-3566","The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, aka the \"POODLE\" issue.","LOW",3.4,0.99999,"2014-10-15T00:55:02.137+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2014-3566","13",true]