[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fmcqOewmkqgrxOZ7c9JH1nP2YUTZaWEJUBv660XsXRTY":3},{"product":4,"cycleMajor":14,"releases":15,"cves":28,"nextMajor":59},{"id":5,"slug":6,"name":7,"category":8,"vendor":9,"description":10,"logo_url":11,"official_url":9,"synced_at":12,"created_at":13},"869a0b9c-2a21-449a-95c3-5745623dacd4","ubuntu","Ubuntu","os",null,"Developers rely on a stable and secure operating system to build and deploy their applications, and one popular choice is a Linux distribution that has been around since 2004. Created by a British company and a community of contributors, this operating system is based on Debian and composed primarily of free and open-source software. Under a meritocratic governance model, new versions are regularly released, with the latest stable version being 22.04.5. With a large community of users and contributors, this operating system is widely used in various environments, from desktops to servers, due to its flexibility and customizability.\n\nThe end-of-life landscape for this operating system is complex, with a total of 44 versions released so far. Out of these, 40 versions have already reached their end-of-life, which means they no longer receive security updates or support. Currently, only 4 versions are still active and supported, with the next version to expire being 25.10, which will reach its end-of-life on 2026-07-01. This means that developers who are still using this version should start planning their upgrade to a newer version to ensure they continue to receive security updates and support. The last version to reach its end-of-life was 25.04, which expired on 2026-01-17.\n\nThe security picture for this operating system is a concern, with a total of 161 CVEs tracked, out of which 12 are critical. The most affected version is 14.04, which has 15 CVEs, highlighting the importance of keeping the operating system up-to-date. Developers should take action to ensure they are running a supported version and apply security patches regularly to protect their systems from potential vulnerabilities. Additionally, they should monitor the Known Exploited Vulnerabilities catalog for any updates related to this operating system, and take prompt action to mitigate any known vulnerabilities.","https:\u002F\u002Fcdn.simpleicons.org\u002Fubuntu","2026-07-17T02:10:37.93+00:00","2026-05-30T16:23:56.027772+00:00","15",[16,23],{"id":17,"product_id":5,"cycle":18,"release_date":19,"eol":20,"eol_boolean":9,"latest":18,"latest_release_date":19,"lts":21,"support":20,"created_at":22},"11c013e3-5b91-4282-ba02-c83a8fe2ff33","15.10","2015-10-22","2016-07-28",false,"2026-05-30T16:26:03.614798+00:00",{"id":24,"product_id":5,"cycle":25,"release_date":26,"eol":27,"eol_boolean":9,"latest":25,"latest_release_date":26,"lts":21,"support":27,"created_at":22},"0b4d29fb-de00-4bd9-ac34-668997d7219b","15.04","2015-04-23","2016-02-04",[29,38,39,45,53],{"cveId":30,"releaseId":24,"cycle":25,"description":31,"severity":32,"cvssScore":33,"epssScore":34,"inKev":35,"publishedAt":36,"url":37},"CVE-2026-31431","In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: algif_aead - Revert to operating out-of-place\n\nThis mostly reverts commit 72548b093ee3 except for the copying of\nthe associated data.\n\nThere is no benefit in operating in-place in algif_aead since the\nsource and destination come from different mappings.  Get rid of\nall the complexity added for in-place operation and just copy the\nAD directly.","HIGH",7.8,0.96267,true,"2026-04-22T09:16:21.27+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-31431",{"cveId":30,"releaseId":17,"cycle":18,"description":31,"severity":32,"cvssScore":33,"epssScore":34,"inKev":35,"publishedAt":36,"url":37},{"cveId":40,"releaseId":17,"cycle":18,"description":41,"severity":32,"cvssScore":33,"epssScore":42,"inKev":21,"publishedAt":43,"url":44},"CVE-2015-8325","The do_setup_env function in session.c in sshd in OpenSSH through 7.2p2, when the UseLogin feature is enabled and PAM is configured to read .pam_environment files in user home directories, allows local users to gain privileges by triggering a crafted environment for the \u002Fbin\u002Flogin program, as demonstrated by an LD_PRELOAD environment variable.",0.00627,"2016-05-01T01:59:00.143+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2015-8325",{"cveId":46,"releaseId":24,"cycle":25,"description":47,"severity":48,"cvssScore":49,"epssScore":50,"inKev":21,"publishedAt":51,"url":52},"CVE-2015-4000","The TLS protocol 1.2 and earlier, when a DHE_EXPORT ciphersuite is enabled on a server but not on a client, does not properly convey a DHE_EXPORT choice, which allows man-in-the-middle attackers to conduct cipher-downgrade attacks by rewriting a ClientHello with DHE replaced by DHE_EXPORT and then rewriting a ServerHello with DHE_EXPORT replaced by DHE, aka the \"Logjam\" issue.","LOW",3.7,0.9986,"2015-05-21T00:59:00.087+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2015-4000",{"cveId":54,"releaseId":24,"cycle":25,"description":55,"severity":48,"cvssScore":49,"epssScore":56,"inKev":21,"publishedAt":57,"url":58},"CVE-2015-2808","The RC4 algorithm, as used in the TLS protocol and SSL protocol, does not properly combine state data with key data during the initialization phase, which makes it easier for remote attackers to conduct plaintext-recovery attacks against the initial bytes of a stream by sniffing network traffic that occasionally relies on keys affected by the Invariance Weakness, and then using a brute-force approach involving LSB values, aka the \"Bar Mitzvah\" issue.",0.73851,"2015-04-01T02:00:35.097+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2015-2808","16"]