dbcve.org
TraefikApplication

CVE-2026-44774

CRITICAL · 9.9 CVSS v3.1 Published 2026-05-15
Fix available
A fix is available. Upgrade to 2.11.46 / 3.6.17 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

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
Traefik is an HTTP reverse proxy and load balancer. Prior to 2.11.46, 3.6.17, and 3.7.1, Traefik's Kubernetes Gateway API provider allows a tenant with HTTPRoute creation permissions to expose the REST provider handler, bypassing the providers.rest.insecure=false setting. The Gateway provider accepts any TraefikService backend reference whose name ends with @internal, making it possible to route traffic to rest@internal in addition to the intended api@internal. In shared Gateway deployments where the REST provider is enabled, this allows a low-privileged actor to gain live dynamic configuration write access to Traefik, enabling unauthorized reconfiguration of routers and services. This vulnerability is fixed in 2.11.46, 3.6.17, and 3.7.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

Traefik's Kubernetes Gateway API provider allows tenants with HTTPRoute creation permissions to bypass the providers.rest.insecure=false setting by using TraefikService backend references ending with @internal (such as rest@internal), enabling unauthorized dynamic configuration write access to the REST provider.

MitigationUpgrade to Traefik 2.11.46, 3.6.17, or 3.7.1 or later. In shared Gateway deployments, restrict HTTPRoute creation permissions until patching is complete.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TraefikApplication
Affected:< 2.11.46>= 3.0.0, < 3.6.17>= 3.7.0, < 3.7.1

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 installed Traefik version
    Run 'traefik --version' or check the image tag/version in your Kubernetes deployment (e.g., kubectl get deployment traefik -o jsonpath="{.spec.template.spec.containers[0].image}")
    Affected if The version is less than 2.11.46, or between 3.0.0 and 3.6.16 inclusive, or between 3.7.0 and 3.7.0 inclusive
  2. Verify REST provider is configured
    Check your Traefik static or dynamic configuration for 'providers.rest' settings. Look in your configuration files, Helm values (providers.rest), or environment variables (TRAEFIK_PROVIDERS_REST_*)
    Affected if The REST provider is explicitly configured in your Traefik configuration
  3. Confirm insecure mode is disabled
    Check if 'providers.rest.insecure' is set to 'false' in your Traefik configuration files, Helm values, or environment variables
    Affected if providers.rest.insecure is explicitly set to false (the secure default)
  4. Check if Kubernetes Gateway API provider is enabled
    Verify 'providers.kubernetesgateway' is enabled or if the Kubernetes Ingress or CRD providers are in use with Gateway API resources. Look for '--providers.kubernetesgateway' flag or TRAEFIK_PROVIDERS_KUBERNETESGATEWAY environment variable
    Affected if The Kubernetes Gateway API provider (kubernetesgateway) is enabled
  5. Review HTTPRoute resources for suspicious backend references
    List all HTTPRoute resources in your cluster (kubectl get httproutes -A -o yaml) and examine any backendRefs that reference TraefikService with '@internal' suffix (e.g., myservice@internal)
    Affected if Any HTTPRoute resource contains a TraefikService backend reference ending with @internal pointing to rest or other internal services

You are affected if running a vulnerable Traefik version AND the REST provider is configured with insecure=false AND you have Gateway API resources that could contain TraefikService backend references with @internal suffix.

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
Upgrade available Upgrade to 2.11.46 / 3.6.17 / 3.7.1 or later
Fixed in 2.11.463.6.173.7.1
Vendor patch github.com →
Interim mitigation

Upgrade to Traefik 2.11.46, 3.6.17, or 3.7.1 or later. In shared Gateway deployments, restrict HTTPRoute creation permissions until patching is complete.

Recommended fix High confidence

2.11.46 (for v2.x), 3.6.17 (for v3.0-3.6), or 3.7.1 (for v3.7)

  1. 1. Identify the current Traefik version by running `traefik version` or checking your deployment configuration
  2. 2. For Traefik v2.x users: If running a version < 2.11.46, upgrade to version 2.11.46
  3. 3. For Traefik v3.0.0-3.6.x users: If running version >= 3.0.0 and < 3.6.17, upgrade to version 3.6.17
  4. 4. For Traefik v3.7.0 users: If running version >= 3.7.0 and < 3.7.1, upgrade to version 3.7.1
  5. 5. Deploy the upgraded Traefik image or binary
  6. 6. Restart the Traefik service to apply the new version
  7. 7. Verify the fix by running `traefik version` and confirming the version number matches the target fixed release

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

Fix this in Traefik Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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