Skip to main content
VulnerabilityPublished

gitlab.com/uniget-org/cli · uniget CLI: Metadata signature verification only runs when UNIGET_IGNORE_METADATA_SIGNATURE is set

Affects gitlab.com/uniget-org/cliSource GCVE Database

0

CVSS 7.8 High : upgrade to 0.28.9 soon.

Data as of 17 Aug 2026, 22:41 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.28.9
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

What to do

Upgrade gitlab.com/uniget-org/cli to 0.28.9.

Affected software

ProductAffectedFixed in
Gogitlab.com/uniget-org/cliAffected
  • >=0.27.4 <0.28.9
Fixed in
  • 0.28.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available that restores the correct logic to ensure signature verification runs unless explicitly disabled. Users should upgrade to uniget version 0.28.9 or later where this issue is fixed. Until patched, avoid running uniget with untrusted metadata sources or setting the UNIGET_IGNORE_METADATA_SIGNATURE environment variable. The vendor advisory confirms a fix is available; apply the official update to remediate this vulnerability.

Description

A logic error in the uniget CLI causes metadata signature verification to run only when the environment variable UNIGET_IGNORE_METADATA_SIGNATURE is set, which is the opposite of the intended behavior. This flaw allows unverified, potentially malicious metadata.json files to be loaded and executed, leading to arbitrary command execution as the user running uniget. The issue affects uniget versions from 0.27.4 up to, but not including, 0.28.9. A patch is available to correct this verification logic.

References

Community reviews

Loading reviews…