2 days 3 hours ago
It was discovered that ngIRCd incorrectly handled SERVER commands without a
prefix, leading to an out-of-bounds read. A remote attacker could possibly
use this issue to cause ngIRCd to crash, resulting in a denial of service.
2 days 3 hours ago
It was discovered that the Murmur server in Mumble did not rate limit
certain client messages. A remote attacker could possibly use this issue to
cause Murmur to hang or crash, resulting in a denial of service. This
update adds a message rate limit, which can be configured with the
messageburst and messagelimit settings.
2 days 10 hours ago
2 days 10 hours ago
2 days 10 hours ago
2 days 15 hours ago
2 days 15 hours ago
2 days 16 hours ago
USN-9004-1 fixed vulnerabilities in OpenJDK 25. Unfortunately, the fix
included an unnecessary debuginfo file. This update fixes the problem.
We apologize for the inconvenience.
Original advisory details:
It was discovered that the 2D component of OpenJDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to
cause a denial of service or to read or modify sensitive data.
(CVE-2026-91415)
It was discovered that the Networking component of OpenJDK 25 did not
correctly authenticate users. A remote attacker could possibly use this
issue to modify sensitive data. (CVE-2026-91398)
It was discovered that the 2D component of OpenJDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to
cause a denial of service or to modify sensitive data. (CVE-2026-91382)
It was discovered that the JGSS component of OpenJDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to
cause a denial of service or to modify sensitive data. (CVE-2026-91411)
It was discovered that the Networking component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service or to modify sensitive data. (CVE-2026-83395)
It was discovered that the Security component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-83381, CVE-2026-87294)
It was discovered that the JAXP component of OpenJDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to read
sensitive data. (CVE-2026-87290)
It was discovered that the JDBC component of OpenJDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to read
sensitive data. (CVE-2026-83387)
It was discovered that the JGSS component of OpenJDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to
modify sensitive data. (CVE-2026-91462)
It was discovered that the Security component of OpenJDK 25 did not
correctly authenticate users. A remote attacker could possibly use this
issue to modify sensitive data. (CVE-2026-83374)
It was discovered that the Libraries component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service. (CVE-2026-91410)
It was discovered that the Networking component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to modify sensitive data. (CVE-2026-87292, CVE-2026-91332, CVE-2026-91451,
CVE-2026-91452)
It was discovered that the JSSE component of OpenJDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to cause a
denial of service. (CVE-2026-91373)
It was discovered that the JAAS component of OpenJDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to read
sensitive data. (CVE-2026-83380)
It was discovered that the JAXP component of OpenJDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to cause a
denial of service. (CVE-2026-83400)
It was discovered that the JGSS component of OpenJDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to read
sensitive data. (CVE-2026-91463, CVE-2026-91464)
It was discovered that the Lightweight HTTP Server component of OpenJDK 25
did not correctly authorize users. A remote attacker could possibly use
this issue to modify sensitive data. (CVE-2026-91453)
It was discovered that the ImageIO component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service. (CVE-2026-91418)
It was discovered that the Compiler component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-91487)
It was discovered that the Serviceability component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-91374)
It was discovered that the Libraries component of OpenJDK 25 did not
correctly authenticate users. A local attacker could possibly use this
issue to modify sensitive data. (CVE-2026-91375)
It was discovered that the JDK tools component of OpenJDK 25 did not
correctly authenticate users. A local attacker could possibly use this
issue to modify sensitive data. (CVE-2026-91379)
It was discovered that the Utility component of OpenJDK 25 did not
correctly authorize users. A local attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-91380)
It was discovered that the ImageIO component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to read sensitive data. (CVE-2026-91334)
It was discovered that the JAXP component of OpenJDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to modify
sensitive data. (CVE-2026-87367)
It was discovered that the JSSE component of OpenJDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to modify
sensitive data. (CVE-2026-83376, CVE-2026-91461)
It was discovered that the Serviceability component of OpenJDK 25 did not
correctly authorize users. A local attacker could possibly use this issue
to cause a denial of service or to modify sensitive data. (CVE-2026-91397)
It was discovered that the Sound component of OpenJDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to cause a
denial of service. (CVE-2026-91400)
It was discovered that the AWT component of OpenJDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to read
sensitive data. (CVE-2026-91335)
It was discovered that the Networking component of OpenJDK 25 did not
correctly authenticate users. A remote attacker could possibly use this
issue to read sensitive data. (CVE-2026-91394)
It was discovered that the Networking component of OpenJDK 25 did not
correctly authorize users. An unauthenticated remote attacker could
possibly use this issue to read sensitive data. (CVE-2026-87291)
It was discovered that the Compiler component of OpenJDK 25 did not
correctly authorize users. An unauthenticated remote attacker could
possibly use this issue to read or modify sensitive data. (CVE-2026-83378)
It was discovered that the Compiler component of OpenJDK 25 did not
correctly authorize users. An unauthenticated remote attacker could
possibly use this issue to read sensitive data. (CVE-2026-87255)
It was discovered that the Security component of OpenJDK 25 did not
correctly authorize users. An unauthenticated remote attacker could
possibly use this issue to read or modify sensitive data. (CVE-2026-91333)
It was discovered that the JSSE component of OpenJDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to read
or modify sensitive data. (CVE-2026-91403)
In addition to security fixes, the updated packages contain bug fixes, new
features, and possibly incompatible changes.
Please see the following for more information:
https://openjdk.org/groups/vulnerability/advisories/2026-10-20
https://openjdk.org/groups/vulnerability/advisories/2026-10-21
https://openjdk.org/groups/vulnerability/advisories/2026-10-24
2 days 19 hours ago
It was discovered that the Security component of CRaC JDK 25 did not
correctly authenticate users. A remote attacker could possibly use this
issue to read or modify sensitive data. (CVE-2026-114820)
It was discovered that the Security component of CRaC JDK 25 did not
correctly authenticate users. A remote attacker could possibly use this
issue to modify sensitive data. (CVE-2026-83374)
It was discovered that the JSSE component of CRaC JDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to modify
sensitive data. (CVE-2026-83376, CVE-2026-91461)
It was discovered that the Compiler component of OpenJDK 25 did not
correctly authorize users. An unauthenticated remote attacker could
possibly use this issue to read or modify sensitive data. (CVE-2026-83378)
It was discovered that the JAAS component of CRaC JDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to read
sensitive data. (CVE-2026-83380)
It was discovered that the Security component of CRaC JDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-83381, CVE-2026-87294)
It was discovered that the JDBC component of CRaC JDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to read
sensitive data. (CVE-2026-83387)
It was discovered that the Networking component of CRaC JDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service or to modify sensitive data. (CVE-2026-83395)
It was discovered that the JAXP component of CRaC JDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to cause a
denial of service. (CVE-2026-83400)
It was discovered that the Compiler component of OpenJDK 25 did not
correctly authorize users. An unauthenticated remote attacker could
possibly use this issue to read sensitive data. (CVE-2026-87255)
It was discovered that the JAXP component of CRaC JDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to read
sensitive data. (CVE-2026-87290)
It was discovered that the Networking component of OpenJDK 25 did not
correctly authorize users. An unauthenticated remote attacker could
possibly use this issue to read sensitive data. (CVE-2026-87291)
It was discovered that the Networking component of CRaC JDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to modify sensitive data. (CVE-2026-87292, CVE-2026-91332, CVE-2026-91451,
CVE-2026-91452)
It was discovered that the JAXP component of CRaC JDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to modify
sensitive data. (CVE-2026-87367)
It was discovered that the Security component of OpenJDK 25 did not
correctly authorize users. An unauthenticated remote attacker could
possibly use this issue to read or modify sensitive data. (CVE-2026-91333)
It was discovered that the ImageIO component of CRaC JDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to read sensitive data. (CVE-2026-91334)
It was discovered that the AWT component of CRaC JDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to read
sensitive data. (CVE-2026-91335)
It was discovered that the JSSE component of CRaC JDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to cause a
denial of service. (CVE-2026-91373)
It was discovered that the Serviceability component of CRaC JDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-91374)
It was discovered that the Libraries component of CRaC JDK 25 did not
correctly authenticate users. A local attacker could possibly use this
issue to modify sensitive data. (CVE-2026-91375)
It was discovered that the JDK tools component of CRaC JDK 25 did not
correctly authenticate users. A local attacker could possibly use this
issue to modify sensitive data. (CVE-2026-91379)
It was discovered that the Utility component of CRaC JDK 25 did not
correctly authorize users. A local attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-91380)
It was discovered that the Networking component of CRaC JDK 25 did not
correctly authenticate users. A remote attacker could possibly use this
issue to read sensitive data. (CVE-2026-91394)
It was discovered that the Serviceability component of CRaC JDK 25 did not
correctly authorize users. A local attacker could possibly use this issue
to cause a denial of service or to modify sensitive data. (CVE-2026-91397)
It was discovered that the Networking component of CRaC JDK 25 did not
correctly authenticate users. A remote attacker could possibly use this
issue to modify sensitive data. (CVE-2026-91398)
It was discovered that the Sound component of CRaC JDK 25 did not correctly
authorize users. A remote attacker could possibly use this issue to cause a
denial of service. (CVE-2026-91400)
It was discovered that the Libraries component of CRaC JDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service. (CVE-2026-91410)
It was discovered that the 2D component of CRaC JDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to
cause a denial of service or to read or modify sensitive data.
(CVE-2026-91415)
It was discovered that the ImageIO component of CRaC JDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service. (CVE-2026-91418)
It was discovered that the Lightweight HTTP Server component of CRaC JDK 25
did not correctly authorize users. A remote attacker could possibly use
this issue to modify sensitive data. (CVE-2026-91453)
It was discovered that the JGSS component of CRaC JDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to
modify sensitive data. (CVE-2026-91462)
It was discovered that the JGSS component of CRaC JDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to read
sensitive data. (CVE-2026-91463, CVE-2026-91464)
It was discovered that the Compiler component of CRaC JDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-91487)
It was discovered that the Libraries component of CRaC JDK 25 did not
correctly authorize users. A remote unauthenticated attacker could possibly
use this issue to read or modify sensitive data. (CVE-2026-101516)
In addition to security fixes, the updated packages contain bug fixes, new
features, and possibly incompatible changes.
Please see the following for more information:
https://openjdk.org/groups/vulnerability/advisories/2026-10-20
https://openjdk.org/groups/vulnerability/advisories/2026-10-21
https://openjdk.org/groups/vulnerability/advisories/2026-10-24
2 days 19 hours ago
It was discovered that Mini-XML used unbounded recursion when deleting and
writing XML nodes. An attacker could possibly use these issues to cause
Mini-XML to crash, resulting in a denial of service. These issues only
affected Ubuntu 16.04 LTS. (CVE-2016-4570, CVE-2016-4571)
It was discovered that Mini-XML incorrectly handled certain floating point
values when writing XML nodes, leading to a stack-based buffer overflow. An
attacker could possibly use this issue to cause Mini-XML to crash,
resulting in a denial of service, or possibly execute arbitrary code.
(CVE-2018-20004)
2 days 19 hours ago
USN-8979-1 fixed vulnerabilities in Deluge. Due to a packaging error, the
fixes were not applied in the update for Ubuntu 16.04 LTS. This update
fixes the problem.
Original advisory details:
It was discovered that the web UI in Deluge did not protect against
cross-site request forgery. A remote attacker could possibly use this
issue to trick a user into installing a malicious plugin, resulting in the
execution of arbitrary code. (CVE-2017-7178)
It was discovered that the web UI in Deluge incorrectly handled certain
requests. A remote attacker could possibly use this issue to read
arbitrary files. (CVE-2017-9031)
2 days 19 hours ago
It was discovered that zcat in zutils incorrectly handled the -v option,
leading to a buffer overflow. If a user were tricked into opening a
specially crafted compressed file, an attacker could possibly use this
issue to cause a denial of service or execute arbitrary code.
2 days 19 hours ago
It was discovered that ZBar incorrectly handled certain QR codes, leading
to a heap-based buffer overflow. If a user or automated system were tricked
into scanning a specially crafted QR code, an attacker could possibly use
this issue to obtain sensitive information or execute arbitrary code.
2 days 19 hours ago
It was discovered that YADIFA did not check for infinite pointer loops when
parsing DNS packets. A remote attacker could possibly use this issue to
cause YADIFA to consume excessive CPU resources, leading to a denial of
service.
2 days 19 hours ago
It was discovered that Syntastic searched the current directory and its
parents for checker configuration files. If a user were tricked into
checking a file in a directory controlled by an attacker, the attacker
could possibly use this issue to execute arbitrary code. After this update,
Syntastic only reads checker configuration files that are named in the
*_config_file options.
2 days 19 hours ago
It was discovered that tmpreaper incorrectly handled certain mount
operations, leading to a race condition. A local attacker could possibly
use this issue to create arbitrary files, leading to privilege escalation.
2 days 19 hours ago
It was discovered that RenderDoc did not properly verify array sizes when
serialising strings, leading to an integer overflow. An attacker could
possibly use this issue to cause a buffer overflow, resulting in a denial
of service, or possibly execute arbitrary code. (CVE-2023-33863)
It was discovered that RenderDoc incorrectly handled certain socket reads,
leading to an integer overflow. A remote attacker could possibly use this
issue to cause a heap buffer overflow, resulting in a denial of service, or
possibly execute arbitrary code. (CVE-2023-33864)
It was discovered that RenderDoc followed symbolic links when opening its
log file in the /tmp/RenderDoc directory. A local attacker could possibly
use this issue to escalate privileges. (CVE-2023-33865)
2 days 23 hours ago
Version:next-20261116 (linux-next)
Released:2026-11-16
3 days 15 hours ago
3 days 22 hours ago