dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-45152

HIGH · 7.8 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
uniget is a universal installer and updater for (container) tools. Prior to 0.27.1, a command injection vulnerability exists in uniget due to unsafe execution of the check field from metadata files using /bin/bash -c. Because the check field is loaded directly from untrusted JSON metadata without validation or sanitization, an attacker can craft malicious metadata that executes arbitrary shell commands on the victim’s system when common uniget operations such as describe, install, update, or inspect are performed. This vulnerability can lead to arbitrary code execution with the privileges of the user running uniget. This vulnerability is fixed in 0.27.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in uniget versions prior to 0.27.1 where the 'check' field from JSON metadata files is executed directly via /bin/bash -c without any validation or sanitization. Attackers can craft malicious metadata to achieve arbitrary code execution when users perform common operations like describe, install, update, or inspect.

MitigationUpgrade to uniget version 0.27.1 or later to patch the vulnerability. Until then, avoid using untrusted or unverified metadata sources with uniget.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify uniget binary location and version
    Run `which uniget` to locate the binary, then execute `uniget --version` or `uniget -v` to retrieve the installed version number
    Affected if The version shown is lower than 0.27.1 (e.g., 0.27.0, 0.26.x, etc.)
  2. Confirm uniget processes JSON metadata files
    Run `uniget --help` or inspect the binary usage to see if it supports describe, install, update, or inspect commands that read metadata
    Affected if Any of these commands are available, as they trigger parsing of metadata containing the 'check' field
  3. Verify the vulnerable code path exists
    Inspect the uniget binary or source for direct execution of the 'check' field via `/bin/bash -c` during metadata parsing (strings grep, if binary is accessible)
    Affected if The binary contains references to bash execution of metadata check fields and processes JSON metadata without validation
  4. Identify metadata sources in use
    Check any existing uniget configuration files or known metadata repositories used by the installation (e.g., `~/.uniget/`, `/etc/uniget/`, or environment-defined paths)
    Affected if Untrusted or unverified metadata sources are configured, as malicious 'check' fields could be injected

You are affected if uniget version is below 0.27.1 and you use commands that parse JSON metadata (describe, install, update, or inspect), since the 'check' field gets executed via /bin/bash without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to uniget version 0.27.1 or later to patch the vulnerability. Until then, avoid using untrusted or unverified metadata sources with uniget.

Recommended fix High confidence

uniget version 0.27.1 or later

  1. Check the currently installed version of uniget by running: uniget --version
  2. Upgrade uniget to version 0.27.1 or later using your package manager or installation method
  3. Verify the upgrade was successful by running: uniget --version and confirming the version number is 0.27.1 or higher
  4. After upgrading, ensure any automated workflows or scripts that fetch or process uniget metadata files are updated to use the patched version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45152 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45152 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data