dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-44592

CRITICAL · 9.4 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Gradient is a nix-based continuous integration system. In 1.1.0, when GRADIENT_DISCOVERABLE=true (the default, and the NixOS module default), anyone who can reach /proto can register as a worker without any credentials by sending a fresh, never-registered worker UUID. The resulting session has PeerAuth::Open, i.e. it sees jobs from every organisation, and can immediately NarPush/NarUploaded arbitrary store paths into nar_storage and the cached_path table. This vulnerability is fixed in 1.1.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

This is an authentication bypass in Gradient's worker registration. When GRADIENT_DISCOVERABLE=true (the default), any unauthenticated attacker who can reach /proto can register a new worker by sending a fresh UUID, gaining PeerAuth::Open access that allows viewing all organizational jobs and injecting arbitrary store paths into the nar storage.

MitigationUpgrade to Gradient 1.1.1 immediately. As a workaround, disable GRADIENT_DISCOVERABLE if possible, though this may affect worker discovery.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Check GRADIENT_DISCOVERABLE setting
    Inspect the GRADIENT_DISPLAYABLE environment variable in your Gradient deployment configuration or environment files. Look for GRADIENT_DISCOVERABLE=true or check if it is unset (default is true).
    Affected if GRADIENT_DISCOVERABLE is set to true or is unset (defaults to true)
  2. Verify /proto endpoint exposure
    Determine if the /proto endpoint is network-accessible from untrusted networks. This typically involves checking your reverse proxy, firewall rules, or network ACLs that expose the Gradient service.
    Affected if The /proto endpoint is reachable from an untrusted network or the internet
  3. Confirm worker registration is enabled
    Check if worker registration functionality is enabled in your Gradient configuration. This is typically controlled by the same GRADIENT_DISCOVERABLE setting or related worker configuration.
    Affected if Worker registration is enabled via GRADIENT_DISCOVERABLE or related settings
  4. Check installed Gradient version
    Run 'gradient --version' or check the deployed Docker image/container tag to identify the exact version number.
    Affected if The installed version is earlier than 1.1.1

You are affected if GRADIENT_DISPLAYABLE is enabled (or defaults to true) AND the /proto endpoint is accessible AND your version is earlier than 1.1.1.

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 Gradient 1.1.1 immediately. As a workaround, disable GRADIENT_DISCOVERABLE if possible, though this may affect worker discovery.

Recommended fix High confidence

1.1.1

  1. Identify the current Gradient version (likely 1.1.0) by checking the installed package or container image tag
  2. Upgrade Gradient to version 1.1.1 or later by updating the package, container image, or NixOS module
  3. Restart the Gradient services to apply the updated version
  4. Verify the upgrade was successful by checking the running version
  5. If using the NixOS module, ensure the module is updated to the version containing the fix

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44592 — 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-44592 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