Skip to main content
CVE-2025-55159VulnerabilityPublished Updated

SUSE · Recommended update of flake-pilot

Affects SUSESource GCVE Database

0
Compare
Authoritative record:CVE-2025-55159· Medium 5.1

Not known to be exploited · CVSS 5.1 Medium.

Data as of 15 Nov 2026, 22:50 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

Description

This update for flake-pilot fixes the following issues: Update version to 3.1.22. - Fixes to use flakes as normal user Running a flake is a container based instance provisioning and startup. Some part of this process requires root permissions for example mounting the container instance store for the provisioning step. This commit fixes the required calls to be properly managed by sudo. - seed from entropy - Fix assignment of random sequence number We should use a seed for the sequence as described in https://rust-random.github.io/book/guide-seeding.html#a-simple-number In addition the logic when a random sequence number should be used was wrong and needed a fix regarding resume and attach type flakes which must not use a random sequence - Pass --init option for resume type flakes In resume mode a sleep command is used to keep the container open. However, without the --init option there is no signal handling available. This commit fixes it - Revert "kill prior remove when using %remove flag" This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2. no hard killing needed with the event loop entrypoint - Fixed CVE-2025-55159 slab: incorrect bounds check Update to slab 0.4.11 to fix the mentioned CVE. This Fixes bsc#1248004 - Apply clippy fixes - Create sequence number for the same invocation If a flake which is not a resume or attach flake is called twice with the same invocation arguments an error message is displayed to give this invocation a new name via the @NAME runtime option. This commit makes this more comfortable and automatically assigns a random sequence number for the call if no @NAME is given. - kill prior remove when using %remove flag In case the container instance should be removed via the %remove flag, send a kill first, followed by a force remove. The reason for this is because we use a never ending sleep command as entry point for resume type containers. If they should be removed the standard signal send on podman rm will not stop the sleep and after a period of 10 seconds podman sends a kill signal itself. We can speedup this process as we know the entry point command and send the kill signal first followed by the remove which saves us some wait time spent in podman otherwise. - Fix clippy hints variables can be used directly in the format! string - Prune old images after load Make sure no <none> image references stay in the registry

References

Community reviews

Loading reviews…