Overview 4,252 matches · 118 in Waratek scope · 76 protected · 83 exploited · 47 CISA KEV · 288 public PoC · 138 EPSS ≥ 0.5
4,252matches
118in Waratek scope2.8%
76protected1.8%
83exploited2.0%
47CISA KEV1.1%
288public PoC6.8%
138EPSS ≥ 0.53.2%
Protected by Waratek
77
1.8%
Rule in development
0
0.0%
Mitigation candidate
2
0.0%
No exploit published
39
0.9%
Outside Waratek scope
465
10.9%
Not applicable
3,669
86.3%
Withdrawn CVE
0
0.0%
blocked by ARMR today
76
1.8%
partly blocked
1
0.0%
not blocked
4,175
98.2%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 883 / year
20041
Not applicable1
Critical1
not blocked1
No public exploit1
200517
Not applicable17
Critical1
High8
Medium6
Low2
not blocked17
Working exploit published2
No public exploit15
200627
Not applicable27
High12
Medium12
Low3
not blocked27
Working exploit published5
Forecast only1
No public exploit21
200749
Outside Waratek scope1
Not applicable48
Critical1
High22
Medium24
Low2
not blocked49
Working exploit published6
Forecast only1
No public exploit42
200876
Outside Waratek scope1
Not applicable75
Critical3
High40
Medium31
Low2
not blocked76
Working exploit published7
No public exploit69
200957
No exploit published1
Not applicable56
Critical1
High23
Medium28
Low5
not blocked57
Exploited3
Working exploit published10
No public exploit44
2010103
Outside Waratek scope2
Not applicable101
Critical5
High36
Medium49
Low13
not blocked103
Exploited6
Working exploit published14
No public exploit83
201143
Outside Waratek scope1
Not applicable42
Critical1
High18
Medium22
Low2
not blocked43
Exploited3
Working exploit published3
Proof of concept only1
Forecast only1
No public exploit35
2012119
Protected by Waratek1
Not applicable118
High66
Medium48
Low5
blocked by ARMR today1
not blocked118
Working exploit published2
No public exploit117
2013200
Protected by Waratek2
Outside Waratek scope6
Not applicable192
Critical7
High64
Medium118
Low11
blocked by ARMR today2
not blocked198
Exploited4
Working exploit published10
Forecast only2
No public exploit184
2014253
Protected by Waratek1
No exploit published2
Outside Waratek scope24
Not applicable226
Critical11
High77
Medium131
Low34
blocked by ARMR today1
not blocked252
Exploited7
Working exploit published8
Proof of concept only1
Forecast only2
No public exploit235
2015347
Protected by Waratek2
No exploit published3
Outside Waratek scope22
Not applicable320
Critical2
High128
Medium181
Low36
blocked by ARMR today2
not blocked345
Exploited4
Working exploit published4
Proof of concept only2
Forecast only1
No public exploit336
2016338
Protected by Waratek4
No exploit published9
Outside Waratek scope7
Not applicable318
Critical26
High157
Medium142
Low13
blocked by ARMR today4
not blocked334
Exploited9
Working exploit published27
Proof of concept only2
Forecast only9
No public exploit291
2017252
Protected by Waratek3
No exploit published6
Outside Waratek scope6
Not applicable237
Critical34
High96
Medium120
Low2
blocked by ARMR today2
partly blocked1
not blocked249
Exploited2
Working exploit published16
Forecast only1
No public exploit233
2018883
Protected by Waratek25
No exploit published2
Outside Waratek scope111
Not applicable745
Critical128
High342
Medium401
Low12
blocked by ARMR today25
not blocked858
Exploited13
Working exploit published41
Proof of concept only3
Forecast only4
No public exploit822
2019703
Protected by Waratek16
No exploit published6
Outside Waratek scope158
Not applicable523
Critical93
High281
Medium304
Low25
blocked by ARMR today16
not blocked687
Exploited10
Working exploit published19
Proof of concept only7
Forecast only11
No public exploit656
2020574
Protected by Waratek23
Mitigation candidate2
No exploit published9
Outside Waratek scope124
Not applicable416
Critical36
High192
Medium298
Low48
blocked by ARMR today23
not blocked551
Exploited7
Working exploit published13
Proof of concept only9
Forecast only7
No public exploit538
202135
No exploit published1
Outside Waratek scope2
Not applicable32
High26
Medium8
Low1
not blocked35
Exploited1
Working exploit published1
Proof of concept only1
No public exploit32
202230
Not applicable30
Critical1
High24
Medium5
not blocked30
Exploited5
Proof of concept only3
No public exploit22
202327
Not applicable27
Critical2
High15
Medium10
not blocked27
Exploited5
Proof of concept only7
No public exploit15
202438
Not applicable38
Critical1
High22
Medium13
Low2
not blocked38
Exploited2
Proof of concept only10
No public exploit26
202529
Not applicable29
Critical3
High12
Medium12
Low2
not blocked29
Exploited1
Proof of concept only16
No public exploit12
202651
Not applicable51
Critical17
High11
Medium15
Low8
not blocked51
Exploited1
Working exploit published1
Proof of concept only22
No public exploit27
200420062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-66897 | Critical | 2026-08-24 | Not applicable | No public exploit | A path traversal vulnerability in LXD's instance template processing allows an attacker with container edit permissions, or any user launching a crafted image, to overwrite arbitrary files on the host system as root. When processing target template paths specified in metadata.yaml, LXD validates the path against a confined os.Root directory handle but subsequently opens and creates the file using os.Create with an unconfined string path. This discrepancy between path resolution checks and file creation allows an attacker to escape directory confinement, overwrite root-owned host files, and achieve host root code execution. |
| CVE-2026-66898 | Critical | 2026-08-12 | Not applicable | Proof of concept only | A path traversal vulnerability in LXD allows an attacker to manipulate file system paths during backup import and restore operations. When importing or restoring a backup archive, LXD fails to validate instance and storage volume names contained within the archive metadata. An attacker can exploit this flaw by supplying a crafted backup archive with malicious instance or volume names containing path traversal sequences, potentially allowing file access or overwriting outside the designated restore directory. |
| CVE-2026-63300 | Critical | 2026-08-12 | Not applicable | Proof of concept only | An improper validation vulnerability in the instancePostMigration function in lxd/instance_post.go of LXD allows an authenticated attacker with can_create_instances permissions on a restricted project to bypass project-level security restrictions. When migrating an instance between projects, LXD fails to validate the instance's configuration against the target project's enforced restrictions (such as restricted.containers.lowlevel, restricted.devices.*, and restricted.networks.access). An attacker can exploit this by creating a disallowed or high-privilege instance in an unrestricted project and subsequently moving it into the restricted project. |
| CVE-2026-63299 | Critical | 2026-08-12 | Not applicable | No public exploit | An authorization bypass vulnerability in LXD allows an authenticated user to bypass project-level disk and volume limits. Two related code paths fail to verify resource limits during volume operations: the storagePoolVolumeTypePostMove function omits the limits.AllowVolumeCreation check before moving a volume across projects, and volume snapshot restore operations skip the AllowVolumeUpdate check when the configuration is nil (Config == nil). An attacker can exploit these flaws to allocate storage resources that exceed the administrative limits configured for a project. |
| CVE-2026-63298 | Critical | 2026-08-12 | Not applicable | Proof of concept only | An improper neutralization of special elements vulnerability in LXD's NVIDIA instance configuration handling allows an authenticated attacker to inject arbitrary configuration directives. By supplying newline characters within the 'nvidia.driver.capabilities' or 'nvidia.require.*' configuration values, an attacker can manipulate the generated lxc.conf file. This flaw enables the attacker to execute arbitrary code on the host system with the privileges of the LXD daemon. |
| CVE-2026-63297 | Critical | 2026-08-12 | Not applicable | Proof of concept only | An authorization bypass vulnerability in LXD due to a timing flaw during configuration merging allows an authenticated attacker to bypass target project restrictions during cross-project instance copies. When copying an instance to a target project, LXD performs restriction checks before configuration merging is complete, creating a time-of-check to time-of-use (TOCTOU) condition. An attacker can exploit this flaw to copy instances with disallowed high-privilege configurations into restricted projects, bypassing security controls. |
| CVE-2026-63296 | Critical | 2026-08-12 | Not applicable | Proof of concept only | An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass target project restrictions during instance migration. When migrating an instance to a target project, LXD accepts configuration overrides without validating the new configuration against the target project's enforced restrictions. An attacker can exploit this flaw to move instances with disallowed high-privilege configurations into restricted projects, bypassing security controls. |
| CVE-2026-63295 | Medium | 2026-08-12 | Not applicable | Proof of concept only | An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the requirement if an instance configuration omits the security.idmap.isolated key. An attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints. |
| CVE-2026-63294 | Critical | 2026-08-12 | Not applicable | Proof of concept only | A link following vulnerability in LXD allows an attacker to achieve root command execution on the host system. During the import or unpacking of crafted image or backup archives, LXD fails to properly validate and confine the backup.yaml file when it exists as a symbolic link. An attacker can exploit this flaw by providing a malicious archive with a symlinked backup.yaml file, causing LXD to process unconfined configuration metadata and execute arbitrary commands with root privileges. |
| CVE-2026-63293 | Critical | 2026-08-12 | Not applicable | Proof of concept only | A link following vulnerability in LXD allows an attacker to achieve arbitrary file read and write operations on the host system. When importing or unpacking an image archive, LXD fails to validate whether the metadata.yaml file is a symbolic link. An attacker can exploit this flaw by providing a crafted image archive with a symlinked metadata.yaml file pointing to target file paths on the host system. |
| CVE-2026-62420 | Critical | 2026-08-12 | Not applicable | No public exploit | An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass target project security restrictions during cross-project instance migrations. When moving an instance cross-project to a different cluster member via POST /1.0/instances/{name} with migration: true, project: <target>, and target: <member>, the destination node skips all project restriction checks because the request arrives as an internal cluster notification. An attacker can exploit this to introduce disallowed instance configurations into a restricted project. |
| CVE-2026-16033 | High | 2026-08-12 | Not applicable | Proof of concept only | A path traversal vulnerability in LXD allows an attacker to achieve arbitrary host file read or unconstrained file creation. When processing image metadata templates, LXD fails to properly sanitize or restrict template file paths from escaping the instance templates directory (specifically affecting virtual machine / QEMU driver execution paths). An attacker can exploit this flaw by providing a crafted image archive with malicious template directives containing path traversal sequences, causing LXD to access or write files outside the intended template directory on the host system. |
| CVE-2026-9640 | High | 2026-06-26 | Not applicable | Proof of concept only | A privilege escalation vulnerability exists in LXD from 6.0 before 6.9, 5.21.0 before 5.21.5, and 5.0.0 before 5.0.7 regarding the handling of project-restriction policies during snapshot restoration.. An authenticated project operator in a restricted multi-tenant environment can bypass policy restrictions by importing a maliciously crafted instance backup containing restricted configuration keys within a snapshot. When the snapshot is restored, these restricted keys are applied to the live instance without policy validation. Starting the modified instance grants the operator unauthorized host root access. |
| CVE-2026-9639 | Medium | 2026-06-26 | Not applicable | Proof of concept only | Nil-pointer dereference in CreateCustomVolumeFromBackup in LXD up to version 6.8 and 5.21 on Linux allows an authenticated user with can_create_storage_volumes permissions to cause a denial of service via a specially crafted custom-volume backup tarball that omits the expires_at snapshot field. |
| CVE-2026-28385 | Medium | 2026-06-26 | Not applicable | No public exploit | In Canonical LXD versions 4.12 through 6.9, a Server-Side Request Forgery (SSRF) vulnerability in the image import functionality allows authenticated users with the can_create_images entitlement to interact with internal network infrastructure via the /images endpoint. When importing an image from a URL source, the LXD daemon fails to validate or restrict outbound destination IP addresses, allowing connections to loopback, RFC1918 private ranges, and cloud metadata endpoints. This enables error-based port scanning and unauthorized interaction with internal HTTP services from the daemon's network position. |
| CVE-2026-12411 | Critical | 2026-06-26 | Not applicable | Proof of concept only | Broken Access Control in the devLXDInstancePatchHandler component of Canonical LXD allows an untrusted guest to mount, read, and overwrite another guest's custom storage volume via a crafted device PATCH request over /dev/lxd when security.devlxd.management.volumes is enabled. |
| CVE-2026-49238 | High | 2026-05-28 | Not applicable | Proof of concept only | An issue was discovered in Canonical Multipass before version 1.16.3. The host-side SFTP server component (sshfs_server), which executes with root privileges on the host, contains a path containment bypass vulnerability within its validate_path function in src/sshfs_mount/sftp_server.cpp. The function performs a plain string prefix comparison on requested paths without path separator validation or dot-dot (..) normalization. A local attacker with root privileges inside a guest virtual machine can bypass the FUSE layer by injecting raw SFTP frames (such as an SSH_FXP_OPEN request) directly into the sshfs_server process stdin/stdout pipes via procfs. By supplying a path containing directory traversal sequences that match the allowed mount prefix, the attacker can force the host-side root process to resolve the traversal and open files outside the designated mount boundary. This allows a guest-side user to read arbitrary files on the host filesystem, resulting in a virtual machine escape. |
| CVE-2026-49237 | High | 2026-05-28 | Not applicable | No public exploit | An issue was discovered in Canonical Multipass for macOS before version 1.16.3 due to an incomplete fix for CVE-2025-5199. While the patch in version 1.16.0 updated the ownership of the multipassd daemon binary to root:wheel, five co-located binaries (multipass, qemu-img, qemu-system-aarch64, qemu-system-x86_64, and sshfs_server) in /Library/Application Support/com.canonical.multipass/bin/ retain ownership by the installing user and remain writable. Because the root LaunchDaemon (com.canonical.multipassd.plist) configures a PATH environment variable that prioritizes this user-writable directory and invokes these auxiliary binaries by their bare names, a local attacker can replace an auxiliary binary (such as qemu-img) with a malicious wrapper. When the root daemon subsequently triggers the binary during routine execution (e.g., via multipass launch), the malicious code executes with root privileges, leading to local privilege escalation. |
| CVE-2026-47337 | Low | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain SAUCE patches with a possible NULL pointer dereference in the handling of AF_INET/AF_INET6 socket mediation. The bug can be triggered by an unprivileged local user. This can lead to a kernel oops. |
| CVE-2026-47336 | Low | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8 contains SAUCE patches with a possible use of an uninitialized variable in AppArmor AF_INET/AF_INET6 socket mediation code. The bug can be triggered by an unprivileged local user and could result in incorrect fine-grained mediation of network sockets. |
| CVE-2026-47335 | Medium | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8 contains SAUCE patches with a possible NULL pointer dereference in the handling of AppArmor notifications. The bug can be triggered by an unprivileged local user. This can lead to a kernel panic. |
| CVE-2026-47334 | Medium | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain AppArmor SAUCE patches which incorrectly sleep while holding a spinlock in notification handling code. The bug can be triggered by an unprivileged local user and can result in kernel panic or deadlock. |
| CVE-2026-47333 | High | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain AppArmor SAUCE patches which can potentially incorrectly compute the size of an internal buffer, leading to a heap memory out-of-bounds read in notification handling code. The bug can be triggered by an unprivileged local user and can result in invalid data being processed by the AppArmor DFA policy engine. |
| CVE-2026-47332 | Medium | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain AppArmor SAUCE patches which incorrectly validate the size of an internal structure, leading to an out-of-bounds read in notification handling code. The bug can be triggered by an unprivileged local user and can result in information disclosure from adjacent slab objects. |
| CVE-2026-47331 | High | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8 contains AppArmor SAUCE patches which fail to acquire a lock when modifying a linked list. An unprivileged local user could trigger the race condition that can lead to a use-after-free (UAF) and, theoretically, arbitrary code execution. |
| CVE-2026-47330 | Low | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 7.17 and 7.0 contain AppArmor SAUCE patches which can, under certain circumstances, use an uninitialized variable in notification handling code. The bug can be triggered by an unprivileged local user and can result in the incorrect caching of AppArmor notification responses. |
| CVE-2026-47329 | Low | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain SAUCE patches which fail to validate invalid sizes of the name field in AppAmor notification responses. The bug can be triggered by an unprivileged local user and could result in handling of crafted responses. |
| CVE-2026-47328 | Medium | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain AppArmor SAUCE patches which incorrectly attempt to free a pointer which was not previously kmalloc()d, while at the same time leaking allocated memory. The bug can be triggered by an unprivileged local user and can result in the corruption of slab metadata and could lead to resource exhaustion. |
| CVE-2026-47327 | Low | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain SAUCE patches with a possible NULL pointer dereference in the handling of AppArmor notifications. The bug can be triggered by an unprivileged local user. This can lead to a kernel oops. |
| CVE-2026-47326 | Medium | 2026-05-28 | Not applicable | No public exploit | Ubuntu Linux 6.8, 6.17 and 7.0 contain SAUCE patches with a memory leak in the handling of big responses to AppArmor notifications. The bug can be triggered by an unprivileged local user. The memory leak could lead to resource exhaustion. |
| CVE-2018-25306 | Medium | 2026-04-29 | Not applicable | Proof of concept only | PDFunite 0.41.0 contains a buffer overflow vulnerability that allows local attackers to crash the application by processing malformed PDF files during merge operations. Attackers can trigger a segmentation fault in the XRef::getEntry function within libpoppler by providing a specially crafted PDF file to the pdfunite utility. |
| CVE-2026-31431 | High | 2026-04-22 | Not applicable | Exploited | In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy the AD directly. |
| CVE-2026-6369 | Medium | 2026-04-20 | Not applicable | No public exploit | An improper access control vulnerability in the canonical-livepatch snap client prior to version 10.15.0 allows a local unprivileged user to obtain a sensitive, root-level authentication token by sending an unauthenticated request to the livepatchd.sock Unix domain socket. This vulnerability is exploitable on systems where an administrator has already enabled the Livepatch client with a valid Ubuntu Pro subscription. This token allows an attacker to access Livepatch services using the victim's credentials, as well as potentially cause issues to the Livepatch server. |
| CVE-2026-5774 | Medium | 2026-04-10 | Not applicable | Proof of concept only | Improper synchronization of the userTokens map in the API server in Canonical Juju 4.0.5, 3.6.20, and 2.9.56 may allow an authenticated user to possibly cause a denial of service on the server or possibly reuse a single-use discharge token. |
| CVE-2026-5412 | Critical | 2026-04-10 | Not applicable | No public exploit | In Juju versions prior to 2.9.57 and 3.6.21, an authorization issue exists in the Controller facade. An authenticated user can call the CloudSpec API method to extract the cloud credentials used to bootstrap the controller. This allows a low-privileged user to access sensitive credentials. This issue is resolved in Juju versions 2.9.57 and 3.6.21. |
| CVE-2026-34179 | Critical | 2026-04-09 | Not applicable | Proof of concept only | In Canonical LXD versions 4.12 through 6.7, the doCertificateUpdate function in lxd/certificates.go does not validate the Type field when handling PUT/PATCH requests to /1.0/certificates/{fingerprint} for restricted TLS certificate users, allowing a remote authenticated attacker to escalate privileges to cluster admin. |
| CVE-2026-34178 | Critical | 2026-04-09 | Not applicable | Proof of concept only | In Canonical LXD before 6.8, the backup import path validates project restrictions against backup/index.yaml in the supplied tar archive but creates the instance from backup/container/backup.yaml, a separate file in the same archive that is never checked against project restrictions. An authenticated remote attacker with instance-creation permission in a restricted project can craft a backup archive where backup.yaml carries restricted settings such as security.privileged=true or raw.lxc directives, bypassing all project restriction enforcement and allowing full host compromise. |
| CVE-2026-34177 | Critical | 2026-04-09 | Not applicable | Proof of concept only | Canonical LXD versions 4.12 through 6.7 contain an incomplete denylist in isVMLowLevelOptionForbidden (lxd/project/limits/permissions.go), which omits raw.apparmor and raw.qemu.conf from the set of keys blocked under the restricted.virtual-machines.lowlevel=block project restriction. A remote attacker with can_edit permission on a VM instance in a restricted project can inject an AppArmor rule and a QEMU chardev configuration that bridges the LXD Unix socket into the guest VM, enabling privilege escalation to LXD cluster administrator and subsequently to host root. |
| CVE-2025-15480 | Low | 2026-04-09 | Not applicable | No public exploit | In Ubuntu, ubuntu-desktop-provision version 24.04.4 could leak sensitive user credentials during crash reporting. Upon installation failure, if a user submitted a bug report to Launchpad, ubuntu-desktop-provision could include the user's password hash in the attached logs. |
| CVE-2025-14551 | Low | 2026-04-09 | Not applicable | No public exploit | In Ubuntu, Subiquity version 24.04.4 could leak sensitive user credentials during crash reporting. Upon installation failure, if a user submitted a bug report to Launchpad, Subiquity could include certain user credentials, such as the user's plaintext Wi-Fi password, in the attached logs. |
| CVE-2025-68153 | High | 2026-04-03 | Not applicable | Proof of concept only | Juju is an open source application orchestration engine that enables any application operation on any infrastructure at any scale through special operators called ‘charms’. From versions 2.9 to before 2.9.56 and 3.6 to before 3.6.19, any authenticated user, machine or controller under a Juju controller can modify the resources of an application within the entire controller. This issue has been patched in versions 2.9.56 and 3.6.19. |
| CVE-2025-68152 | Medium | 2026-04-03 | Not applicable | No public exploit | Juju is an open source application orchestration engine that enables any application operation on any infrastructure at any scale through special operators called ‘charms’. From versions 2.9 to before 2.9.56 and 3.6 to before 3.6.19, it is possible that a compromised workload machine under a Juju controller can read any log file for any entity in any model at any level. This issue has been patched in versions 2.9.56 and 3.6.19. |
| CVE-2026-4370 | Critical | 2026-04-01 | Not applicable | Proof of concept only | A vulnerability was identified in Juju from version 3.2.0 until 3.6.19 and from version 4.0 until 4.0.4, where the internal Dqlite database cluster fails to perform proper TLS client and server authentication. Specifically, the Juju controller's database endpoint does not validate client certificates when a new node attempts to join the cluster. An unauthenticated attacker with network reachability to the Juju controller's Dqlite port can exploit this flaw to join the database cluster. Once joined, the attacker gains full read and write access to the underlying database, allowing for total data compromise. |
| CVE-2026-32694 | Medium | 2026-03-18 | Not applicable | Proof of concept only | In Juju from version 3.0.0 through 3.6.18, when a secret owner grants permissions to a secret to a grantee, the secret owner relies exclusively on a predictable XID of the secret to verify ownership. This allows a malicious grantee which can request secrets to predict past secrets granted by the same secret owner to different grantees, allowing them to use the resources granted by those past secrets. Successful exploitation relies on a very specific configuration, specific data semantic, and the administrator having the need to deploy at least two different applications, one of them controlled by the attacker. |
| CVE-2026-32693 | High | 2026-03-18 | Not applicable | No public exploit | In Juju from version 3.0.0 through 3.6.18, the authorization of the "secret-set" tool is not performed correctly, which allows a grantee to update the secret content, and can lead to reading or updating other secrets. When the "secret-set" tool logs an error in an exploitation attempt, the secret is still updated contrary to expectations, and the new value is visible to both the owner and the grantee. |
| CVE-2026-32692 | High | 2026-03-18 | Not applicable | No public exploit | An authorization bypass vulnerability in the Vault secrets back-end implementation of Juju versions 3.1.6 through 3.6.18 allows an authenticated unit agent to perform unauthorized updates to secret revisions. With sufficient information, an attacker can poison any existing secret revision within the scope of that Vault secret back-end. |
| CVE-2026-32691 | Medium | 2026-03-18 | Not applicable | No public exploit | A race condition in the secrets management subsystem of Juju versions 3.0.0 through 3.6.18 allows an authenticated unit agent to claim ownership of a newly initialized secret. Between generating a Juju Secret ID and creating the secret's first revision, an attacker authenticated as another unit agent can claim ownership of a known secret. This leads to the attacking unit being able to read the content of the initial secret revision. |
| CVE-2026-3888 | High | 2026-03-17 | Not applicable | Working exploit published | Local privilege escalation in snapd on Linux allows local attackers to get root privilege by re-creating snap's private /tmp directory when systemd-tmpfiles is configured to automatically clean up this directory. This issue affects Ubuntu 16.04 LTS, 18.04 LTS, 20.04 LTS, 22.04 LTS, and 24.04 LTS. |
| CVE-2026-3497 | Medium | 2026-03-12 | Not applicable | No public exploit | Vulnerability in the OpenSSH GSSAPI delta included in various Linux distributions. This vulnerability affects the GSSAPI patches added by various Linux distributions and does not affect the OpenSSH upstream project itself. The usage of sshpkt_disconnect() on an error, which does not terminate the process, allows an attacker to send an unexpected GSSAPI message type during the GSSAPI key exchange to the server, which will call the underlying function and continue the execution of the program without setting the related connection variables. As the variables are not initialized to NULL the code later accesses those uninitialized variables, accessing random memory, which could lead to undefined behavior. The recommended workaround is to use ssh_packet_disconnect() instead, which does terminate the process. The impact of the vulnerability depends heavily on the compiler flag hardening configuration. |
| CVE-2026-28384 | Critical | 2026-03-12 | Not applicable | Proof of concept only | An improper sanitization of the compression_algorithm parameter in Canonical LXD allows an authenticated, unprivileged user to execute commands as the LXD daemon on the LXD server via API calls to the image and backup endpoints. This issue affected LXD from 4.12 through 6.6 and was fixed in the snap versions 5.0.6-e49d9f4 (channel 5.0/stable), 5.21.4-1374f39 (channel 5.21/stable), and 6.7-1f11451 (channel 6.0 stable). The channel 4.0/stable is not affected as it contains version 4.0.10. |
| CVE-2026-3351 | Low | 2026-03-03 | Not applicable | No public exploit | Improper authorization in the API endpoint GET /1.0/certificates in Canonical LXD 6.6 on Linux allows an authenticated, restricted user to enumerate all certificate fingerprints trusted by the lxd server. |
| CVE-2025-5467 | Low | 2025-12-10 | Not applicable | Proof of concept only | It was discovered that process_crash() in data/apport in Canonical's Apport crash reporting tool may create crash files with incorrect group ownership, possibly exposing crash information beyond expected or intended groups. |
| CVE-2025-7044 | High | 2025-12-03 | Not applicable | No public exploit | An Improper Input Validation vulnerability exists in the user websocket handler of MAAS. An authenticated, unprivileged attacker can intercept a user.update websocket request and inject the is_superuser property set to true. The server improperly validates this input, allowing the attacker to self-promote to an administrator role. This results in full administrative control over the MAAS deployment. |
| CVE-2025-54293 | High | 2025-10-02 | Not applicable | Proof of concept only | Path Traversal in the log file retrieval function in Canonical LXD 5.0 LTS on Linux allows authenticated remote attackers to read arbitrary files on the host system via crafted log file names or symbolic links. |
| CVE-2025-54292 | Medium | 2025-10-02 | Not applicable | Proof of concept only | Path traversal in Canonical LXD LXD-UI versions before 6.5 and 5.21.4 on all platforms allows remote authenticated attackers to access or modify unintended resources via crafted resource names embedded in URL paths. |
| CVE-2025-54291 | Medium | 2025-10-02 | Not applicable | Proof of concept only | Information disclosure in images API in Canonical LXD before 6.5 and 5.21.4 on all platforms allows unauthenticated remote attackers to determine project existence via differing HTTP status code responses. |
| CVE-2025-54290 | Medium | 2025-10-02 | Not applicable | Proof of concept only | Information disclosure in image export API in Canonical LXD before 6.5 and 5.21.4 on Linux allows network attackers to determine project existence without authentication via crafted requests using wildcard fingerprints. |
| CVE-2025-54289 | High | 2025-10-02 | Not applicable | No public exploit | Privilege Escalation in operations API in Canonical LXD <6.5 on multiple platforms allows attacker with read permissions to hijack terminal or console sessions and execute arbitrary commands via WebSocket connection hijacking format |
| CVE-2025-54288 | Medium | 2025-10-02 | Not applicable | Proof of concept only | Information Spoofing in devLXD Server in Canonical LXD versions 4.0 and above on Linux container platforms allows attackers with root privileges within any container to impersonate other containers and obtain their metadata, configuration, and device information via spoofed process names in the command line. |
| CVE-2025-54287 | High | 2025-10-02 | Not applicable | Proof of concept only | Template Injection in instance snapshot creation component in Canonical LXD (>= 4.0) allows an attacker with instance configuration permissions to read arbitrary files on the host system via specially crafted snapshot pattern templates using the Pongo2 template engine. |
| CVE-2025-54286 | High | 2025-10-02 | Not applicable | No public exploit | Cross-Site Request Forgery (CSRF) in LXD-UI in Canonical LXD versions >= 5.0 on Linux allows an attacker to create and start container instances without user consent via crafted HTML form submissions exploiting client certificate authentication. |
| CVE-2024-6107 | Critical | 2025-07-21 | Not applicable | Proof of concept only | Due to insufficient verification, an attacker could use a malicious client to bypass authentication checks and run RPC commands in a region. This has been addressed in MAAS and updated in the corresponding snaps. |
| CVE-2025-5199 | High | 2025-07-12 | Not applicable | Proof of concept only | In Canonical Multipass up to and including version 1.15.1 on macOS, incorrect default permissions allow a local attacker to escalate privileges by modifying files executed with administrative privileges by a Launch Daemon during system startup. |
| CVE-2025-53513 | High | 2025-07-08 | Not applicable | Proof of concept only | The /charms endpoint on a Juju controller lacked sufficient authorization checks, allowing any user with an account on the controller to upload a charm. Uploading a malicious charm that exploits a Zip Slip vulnerability could allow an attacker to gain access to a machine running a unit through the affected charm. |
| CVE-2025-53512 | Medium | 2025-07-08 | Not applicable | Proof of concept only | The /log endpoint on a Juju controller lacked sufficient authorization checks, allowing unauthorized users to access debug messages that could contain sensitive information. |
| CVE-2025-0928 | High | 2025-07-08 | Not applicable | Proof of concept only | In Juju versions prior to 3.6.8 and 2.9.52, any authenticated controller user was allowed to upload arbitrary agent binaries to any model or to the controller itself, without verifying model membership or requiring explicit permissions. This enabled the distribution of poisoned binaries to new or upgraded machines, potentially resulting in remote code execution. |
| CVE-2025-6224 | Medium | 2025-07-01 | Not applicable | Proof of concept only | Certificate generation in juju/utils using the cert.NewLeaf function could include private information. If this certificate were then transferred over the network in plaintext, an attacker listening on that network could sniff the certificate and trivially extract the private key from it. |
| CVE-2025-32463 | Critical | 2025-06-30 | Not applicable | Exploited | Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option. |
| CVE-2024-6174 | High | 2025-06-26 | Not applicable | No public exploit | When a non-x86 platform is detected, cloud-init grants root access to a hardcoded url with a local IP address. To prevent this, cloud-init default configurations disable platform enumeration. |
| CVE-2024-11584 | Medium | 2025-06-26 | Not applicable | No public exploit | cloud-init through 25.1.2 includes the systemd socket unit cloud-init-hotplugd.socket with default SocketMode that grants 0666 permissions, making it world-writable. This is used for the "/run/cloud-init/hook-hotplug-cmd" FIFO. An unprivileged user could trigger hotplug-hook commands. |
| CVE-2025-5689 | High | 2025-06-16 | Not applicable | No public exploit | A flaw was found in the temporary user record that authd uses in the pre-auth NSS. As a result, a user login for the first time will be considered to be part of the root group in the context of that SSH session. |
| CVE-2025-5054 | Medium | 2025-05-30 | Not applicable | Proof of concept only | Race condition in Canonical apport up to and including 2.32.0 allows a local attacker to leak sensitive information via PID-reuse by leveraging namespaces. When handling a crash, the function `_check_global_pid_and_forward`, which detects if the crashing process resided in a container, was being called before `consistency_checks`, which attempts to detect if the crashing process had been replaced. Because of this, if a process crashed and was quickly replaced with a containerized one, apport could be made to forward the core dump to the container, potentially leaking sensitive information. `consistency_checks` is now being called before `_check_global_pid_and_forward`. Additionally, given that the PID-reuse race condition cannot be reliably detected from userspace alone, crashes are only forwarded to containers if the kernel provided a pidfd, or if the crashing process was unprivileged (i.e., if dump mode == 1). |
| CVE-2023-5616 | Medium | 2025-04-15 | Not applicable | No public exploit | In Ubuntu, gnome-control-center did not properly reflect SSH remote login status when the system was configured to use systemd socket activation for openssh-server. This could unknowingly leave the local machine exposed to remote SSH access contrary to expectation of the user. |
| CVE-2023-0881 | High | 2025-03-31 | Not applicable | No public exploit | Running DDoS on tcp port 22 will trigger a kernel crash. This issue is introduced by the backport of a commit regarding nft_lookup without the subsequent fixes that were introduced after this commit. The resolution of this CVE introduces those commits to the linux-bluefield package. |
| CVE-2022-1804 | Medium | 2025-03-25 | Not applicable | No public exploit | accountsservice no longer drops permissions when writting .pam_environment |
| CVE-2025-26466 | Medium | 2025-02-28 | Not applicable | Proof of concept only | A flaw was found in the OpenSSH package. For each ping packet the SSH server receives, a pong packet is allocated in a memory buffer and stored in a queue of packages. It is only freed when the server/client key exchange has finished. A malicious client may keep sending such packages, leading to an uncontrolled increase in memory consumption on the server side. Consequently, the server may become unavailable, resulting in a denial of service attack. |
| CVE-2023-0092 | Medium | 2025-01-31 | Not applicable | No public exploit | An authenticated user who has read access to the juju controller model, may construct a remote request to download an arbitrary file from the controller's filesystem. |
| CVE-2022-28653 | High | 2025-01-31 | Not applicable | No public exploit | Users can consume unlimited disk space in /var/crash |
| CVE-2022-1736 | Critical | 2025-01-31 | Not applicable | No public exploit | Ubuntu's configuration of gnome-control-center allowed Remote Desktop Sharing to be enabled by default. |
| CVE-2020-11936 | Low | 2025-01-31 | Not applicable | Proof of concept only | gdbus setgid privilege escalation |
| CVE-2024-6219 | Low | 2024-12-06 | Not applicable | Proof of concept only | Mark Laing discovered in LXD's PKI mode, until version 5.21.1, that a restricted certificate could be added to the trust store with its restrictions not honoured. |
| CVE-2024-6156 | Low | 2024-12-06 | Not applicable | Proof of concept only | Mark Laing discovered that LXD's PKI mode, until version 5.21.2, could be bypassed if the client's certificate was present in the trust store. |
| CVE-2024-9312 | High | 2024-10-10 | Not applicable | No public exploit | Authd, through version 0.3.6, did not sufficiently randomize user IDs to prevent collisions. A local attacker who can register user names could spoof another user's ID and gain their privileges. |
| CVE-2024-9313 | High | 2024-10-03 | Not applicable | No public exploit | Authd PAM module before version 0.3.5 can allow broker-managed users to impersonate any other user managed by the same broker and perform any PAM operation with it, including authenticating as them. |
| CVE-2024-8038 | High | 2024-10-02 | Not applicable | No public exploit | Vulnerable juju introspection abstract UNIX domain socket. An abstract UNIX domain socket responsible for introspection is available without authentication locally to network namespace users. This enables denial of service attacks. |
| CVE-2024-8037 | Medium | 2024-10-02 | Not applicable | No public exploit | Vulnerable juju hook tool abstract UNIX domain socket. When combined with an attack of JUJU_CONTEXT_ID, any user on the local system with access to the default network namespace may connect to the @/var/lib/juju/agents/unit-xxxx-yyyy/agent.socket and perform actions that are normally reserved to a juju charm. |
| CVE-2024-7558 | High | 2024-10-02 | Not applicable | No public exploit | JUJU_CONTEXT_ID is a predictable authentication secret. On a Juju machine (non-Kubernetes) or Juju charm container (on Kubernetes), an unprivileged user in the same network namespace can connect to an abstract domain socket and guess the JUJU_CONTEXT_ID value. This gives the unprivileged user access to the same information and tools as the Juju charm. |
| CVE-2024-8287 | High | 2024-09-18 | Not applicable | No public exploit | Anbox Management Service, in versions 1.17.0 through 1.23.0, does not validate the TLS certificate provided to it by the Anbox Stream Agent. An attacker must be able to machine-in-the-middle the Anbox Stream Agent from within an internal network before they can attempt to take advantage of this. |
| CVE-2024-6984 | High | 2024-07-29 | Not applicable | No public exploit | An issue was discovered in Juju that resulted in the leak of the sensitive context ID, which allows a local unprivileged attacker to access other sensitive data or relation accessible to the local charm. |
| CVE-2024-29069 | High | 2024-07-25 | Not applicable | No public exploit | In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when extracting a snap. The snap format is a squashfs file-system image and so can contain symbolic links and other file types. Various file entries within the snap squashfs image (such as icons and desktop files etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained symbolic links at these paths could then cause snapd to write out the contents of the symbolic link destination into a world-readable directory. This in-turn could allow an unprivileged user to gain access to privileged information. |
| CVE-2024-29068 | Medium | 2024-07-25 | Not applicable | No public exploit | In snapd versions prior to 2.62, snapd failed to properly check the file type when extracting a snap. The snap format is a squashfs file-system image and so can contain files that are non-regular files (such as pipes or sockets etc). Various file entries within the snap squashfs image (such as icons etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained non-regular files at these paths could then cause snapd to block indefinitely trying to read from such files and cause a denial of service. |
| CVE-2024-1724 | High | 2024-07-25 | Not applicable | Proof of concept only | In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. In Ubuntu, when this path exists, it is automatically added to the users PATH. An attacker who could convince a user to install a malicious snap which used the 'home' plug could use this vulnerability to install arbitrary scripts into the users PATH which may then be run by the user outside of the expected snap sandbox and hence allow them to escape confinement. |
| CVE-2024-6714 | High | 2024-07-23 | Not applicable | No public exploit | An issue was discovered in provd before version 0.1.5 with a setuid binary, which allows a local attacker to escalate their privilege. |
| CVE-2024-6387 | High | 2024-07-01 | Not applicable | Exploited | A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). There is a race condition which can lead sshd to handle some signals in an unsafe manner. An unauthenticated, remote attacker may be able to trigger it by failing to authenticate within a set time period. |
| CVE-2024-6388 | Medium | 2024-06-27 | Not applicable | Proof of concept only | Marco Trevisan discovered that the Ubuntu Advantage Desktop Daemon, before version 1.12, leaks the Pro token to unprivileged users by passing the token as an argument in plaintext. |
| CVE-2020-27352 | Critical | 2024-06-21 | Not applicable | No public exploit | When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify Delegate=yes - as a result systemd will move processes from the containers created and managed by these snaps into the cgroup of the main daemon within the snap itself when reloading system units. This may grant additional privileges to a container within the snap that were not originally intended. |
| CVE-2022-4968 | Medium | 2024-06-07 | Not applicable | No public exploit | netplan leaks the private key of wireguard to local users. Versions after 1.0 are not affected. |
| CVE-2022-28658 | Medium | 2024-06-04 | Not applicable | No public exploit | Apport argument parsing mishandles filename splitting on older kernels resulting in argument spoofing |
| CVE-2022-28657 | High | 2024-06-04 | Not applicable | No public exploit | Apport does not disable python crash handler before entering chroot |
| CVE-2022-28656 | Medium | 2024-06-04 | Not applicable | No public exploit | is_closing_session() allows users to consume RAM in the Apport process |