{"id":"EUVD-2026-54293","revision":null,"records":[{"revision":"8392f1c076f3447a82b6bb201f9c45ca","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2026-71325","aliases":[],"title":"Traefik: `allowCrossNamespace=false` bypass via `@kubernetescrd` TraefikService backendRef","description":"Traefik is an open-source edge router that makes publishing services a fun and easy experience. Prior to 2.11.54, 3.6.25, and 3.7.10, cross-namespace @kubernetescrd references are not rejected for TraefikService backend references resolved by the service resolver. A tenant confined by RBAC to a single namespace can therefore bind its own router to a TraefikService owned by another namespace and expose or reroute that namespace's backend, defeating the namespace isolation allowCrossNamespace=false is meant to enforce. This issue is fixed in version 2.11.54, 3.6.25, 3.7.10.","state":0,"publishedAt":"2026-08-06T16:24:56.606+00:00","modifiedAt":"2026-08-07T17:09:50.885+00:00","affected":[{"ecosystem":"Vendor product","name":"traefik","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"traefik\",\n                    \"product\": \"traefik\",\n                    \"versions\": [\n                        {\n                            \"version\": \"< 2.11.54\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 3.0.0, < 3.6.25\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 3.7.0, < 3.7.10\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 4.0","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","score":4.8,"severity":"MEDIUM"}],"references":["https://github.com/traefik/traefik/security/advisories/GHSA-62fc-8686-hfmq","https://github.com/traefik/traefik/commit/65ebf4b47fbdc33e3856803a5844a404e094d52d","https://github.com/traefik/traefik/releases/tag/v2.11.54","https://github.com/traefik/traefik/releases/tag/v3.6.25","https://github.com/traefik/traefik/releases/tag/v3.7.10"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-71325","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-71325","identifiers":["CVE-2026-71325"]},"retained":false,"historicalAffected":[]},{"revision":"d4f1cfb6adea4eb7a451e03f897d44a5","observedAt":"2026-11-11T16:02:18.564+00:00","statement":{"source":"euvd","id":"EUVD-2026-54293","aliases":["CVE-2026-71325","GHSA-62fc-8686-hfmq"],"title":"Traefik is an open-source edge router that makes publishing services a fun and easy experience. Prior to 2.11.54, 3.6.25, and 3.7.10, cross-namespace @kubernetescrd references are not rejected for TraefikService backend references resolved …","description":"Traefik is an open-source edge router that makes publishing services a fun and easy experience. Prior to 2.11.54, 3.6.25, and 3.7.10, cross-namespace @kubernetescrd references are not rejected for TraefikService backend references resolved by the service resolver. A tenant confined by RBAC to a single namespace can therefore bind its own router to a TraefikService owned by another namespace and expose or reroute that namespace's backend, defeating the namespace isolation allowCrossNamespace=false is meant to enforce. This issue is fixed in version 2.11.54, 3.6.25, 3.7.10.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 4.0","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","score":4.8,"severity":null}],"references":["https://github.com/traefik/traefik/security/advisories/GHSA-62fc-8686-hfmq","https://github.com/traefik/traefik/commit/65ebf4b47fbdc33e3856803a5844a404e094d52d","https://github.com/traefik/traefik/releases/tag/v2.11.54","https://github.com/traefik/traefik/releases/tag/v3.6.25","https://github.com/traefik/traefik/releases/tag/v3.7.10"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-54293","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Aug 6, 2026, 4:24:56 PM","dateUpdated":"Aug 7, 2026, 5:09:50 PM"},"relatedAdvisories":[{"id":"RHSA-2026:90321","title":"Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.31.0 Release.","vulnerabilityIds":["CVE-2023-54404","CVE-2025-62718","CVE-2026-8643","CVE-2026-9496","CVE-2026-12185","CVE-2026-13697","CVE-2026-14682","CVE-2026-15076","CVE-2026-16308","CVE-2026-17106","CVE-2026-18427","CVE-2026-19203","CVE-2026-19534","CVE-2026-39820","CVE-2026-41178","CVE-2026-41707","CVE-2026-42499","CVE-2026-42502","CVE-2026-45416","CVE-2026-47884","CVE-2026-47886","CVE-2026-47888","CVE-2026-47890","CVE-2026-47892","CVE-2026-50010","CVE-2026-55831","CVE-2026-55833","CVE-2026-55851","CVE-2026-56745","CVE-2026-56746","CVE-2026-56819","CVE-2026-56852","CVE-2026-56854","CVE-2026-58062","CVE-2026-59280","CVE-2026-59282","CVE-2026-59283","CVE-2026-59296","CVE-2026-59313","CVE-2026-59323","CVE-2026-59651","CVE-2026-59887","CVE-2026-59899","CVE-2026-59901","CVE-2026-62243","CVE-2026-64607","CVE-2026-67213","CVE-2026-67312","CVE-2026-67313","CVE-2026-67314","CVE-2026-67320","CVE-2026-67321","CVE-2026-68494","CVE-2026-68497","CVE-2026-69152","CVE-2026-69192","CVE-2026-71290","CVE-2026-71324","CVE-2026-71325","CVE-2026-71327","CVE-2026-73500","CVE-2026-73508","CVE-2026-74835","CVE-2026-75838","CVE-2026-75899","CVE-2026-75931","CVE-2026-76169","CVE-2026-81521","CVE-2026-82417","CVE-2026-82562","CVE-2026-84292","CVE-2026-84375","CVE-2026-84394","CVE-2026-84428","CVE-2026-84445","CVE-2026-84469","CVE-2026-84504","CVE-2026-84961","CVE-2026-85062","CVE-2026-85124","CVE-2026-85152","CVE-2026-85595","CVE-2026-85597","CVE-2026-86063","CVE-2026-87743","CVE-2026-88004","CVE-2026-88007","CVE-2026-88008","CVE-2026-88009","CVE-2026-88011","CVE-2026-88012","CVE-2026-88031","CVE-2026-88878","CVE-2026-88879","CVE-2026-90711","CVE-2026-93749","CVE-2026-100655","CVE-2026-100656","CVE-2026-100666","CVE-2026-101916","CVE-2026-102925","CVE-2026-102930","CVE-2026-103435","CVE-2026-109618","CVE-2026-109619"]}],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2026-54293","identifiers":["EUVD-2026-54293","CVE-2026-71325","GHSA-62fc-8686-hfmq"]},"retained":false,"historicalAffected":[]},{"revision":"ef0dbada54c442ed83d8f30253c26072","observedAt":"2026-10-25T15:18:57.446+00:00","statement":{"source":"nvd","id":"CVE-2026-71325","aliases":[],"title":"Traefik is an open-source edge router that makes publishing services a fun and easy experience. Prior to 2.11.54, 3.6.25, and 3.7.10, cross-namespace @kubernetescrd references are not rejected for TraefikService backend references resolved …","description":"Traefik is an open-source edge router that makes publishing services a fun and easy experience. Prior to 2.11.54, 3.6.25, and 3.7.10, cross-namespace @kubernetescrd references are not rejected for TraefikService backend references resolved by the service resolver. A tenant confined by RBAC to a single namespace can therefore bind its own router to a TraefikService owned by another namespace and expose or reroute that namespace's backend, defeating the namespace isolation allowCrossNamespace=false is meant to enforce. This issue is fixed in version 2.11.54, 3.6.25, 3.7.10.","state":0,"publishedAt":"2026-08-06T22:18:29.49+00:00","modifiedAt":"2026-09-16T20:46:01.89+00:00","affected":[],"metrics":[{"system":"CVSS 4.0 · security-advisories@github.com · Secondary","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","score":4.8,"severity":"MEDIUM"},{"system":"CVSS 3.1 · nvd@nist.gov · Primary","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","score":4.4,"severity":"MEDIUM"}],"references":["https://github.com/traefik/traefik/commit/65ebf4b47fbdc33e3856803a5844a404e094d52d","https://github.com/traefik/traefik/releases/tag/v2.11.54","https://github.com/traefik/traefik/releases/tag/v3.6.25","https://github.com/traefik/traefik/releases/tag/v3.7.10","https://github.com/traefik/traefik/security/advisories/GHSA-62fc-8686-hfmq"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-71325","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Analyzed","weaknesses":["CWE-653","CWE-863"],"productCriteria":["cpe:2.3:a:traefik:traefik:*:*:*:*:*:*:*:*"],"sourceDates":{"published":"2026-08-06T22:18:29.490","lastModified":"2026-09-16T20:46:01.890"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2026-71325","identifiers":["CVE-2026-71325"]},"retained":false,"historicalAffected":[]},{"revision":"4ac1bceb5db74b79a8a9fb05ba8793cd","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GHSA-62fc-8686-hfmq","aliases":["CVE-2026-71325","GO-2026-6203"],"title":"Traefik: `allowCrossNamespace=false` bypass via `@kubernetescrd` TraefikService backendRef","description":"## Summary\n\nThere is a medium severity vulnerability in Traefik's Kubernetes CRD provider. When `providers.kubernetesCRD.allowCrossNamespace` is disabled — the default — cross-namespace `@kubernetescrd` references are rejected for middlewares, TLS options and HTTP/TCP ServersTransports, but the same restriction was not applied to `TraefikService` backend references resolved by the service resolver. A tenant confined by RBAC to a single namespace can therefore bind its own router to a `TraefikService` owned by another namespace and expose or reroute that namespace's backend, defeating the namespace isolation `allowCrossNamespace=false` is meant to enforce. Traefik v2 releases and the unmaintained v3 minor lines below v3.6 are affected and will not receive a patch on their own line; the remedy for those users is upgrading to a maintained, patched release.\n\n## Patches\n\n- https://github.com/traefik/traefik/releases/tag/v2.11.54\n- https://github.com/traefik/traefik/releases/tag/v3.6.25\n- https://github.com/traefik/traefik/releases/tag/v3.7.10\n\n## For more information\n\nIf you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).\n\n<details>\n<summary>Original Description</summary>\n\n### Summary\nWhen `providers.kubernetesCRD.allowCrossNamespace=false` (the default), Traefik correctly rejects cross-namespace `@kubernetescrd` references for middlewares, TLS options, and HTTP/TCP `ServersTransport`, but it does not apply the same restriction to service (`TraefikService`) backendRefs. As a result, a Kubernetes tenant who is confined by RBAC to their own namespace can bind their own router to a `TraefikService` owned by another namespace simply by referencing it as `<victim-namespace>-<name>@kubernetescrd`, defeating the namespace-isolation boundary that `allowCrossNamespace=false` is meant to enforce.\n\nThis is the service-resolver sibling of the cross-namespace isolation family that Traefik has been fixing one resolver at a time (`df00d82f` / CVE-2026-41174 for Chain middlewares, and `67501cbe` for TCP `ServersTransport`, which shipped in v3.7.7 only four days before the analyzed commit). The `TraefikService` resolver in `configBuilder.nameAndService` was never given the guard its sibling resolvers received.\n\n### Details\n### Root cause\n\n`nameAndService` only performs the same-namespace check (`isNamespaceAllowed`) inside the branch that handles names without an `@` separator. For names that contain an `@` separator (that is, `@kubernetescrd` cross-namespace references) it applies only the `crossProviderNamespaces` allowlist check, and that check returns `true` by default because a `nil` allowlist means \"unrestricted\". It never applies the `!allowCrossNamespace && strings.HasSuffix(name, \"@kubernetescrd\")` rejection that the sibling resolvers all apply, so `allowCrossNamespace=false` is effectively never consulted for `@kubernetescrd` service references.\n\n### Vulnerable code\n\n```go\n// pkg/provider/kubernetes/crd/kubernetes_http.go:662-695 — nameAndService (VULNERABLE)\nfunc (c configBuilder) nameAndService(ctx context.Context, parentNamespace string, service traefikv1alpha1.LoadBalancerSpec) (string, *dynamic.Service, error) {\n\tsvcCtx := log.Ctx(ctx).With().Str(logs.ServiceName, service.Name).Logger().WithContext(ctx)\n\n\tif !strings.Contains(service.Name, providerNamespaceSeparator) { // 665: only names WITHOUT \"@\"\n\t\tservice = *service.DeepCopy()\n\t\tservice.Namespace = namespaceOrParentNamespace(service.Namespace, parentNamespace)\n\t\tif !isNamespaceAllowed(c.allowCrossNamespace, parentNamespace, service.Namespace) { // 669\n\t\t\treturn \"\", nil, fmt.Errorf(\"service %s/%s not in the parent resource namespace %s\", ...)\n\t\t}\n\t}\n\n\t// 674: for \"@\"-names, the ONLY gate is crossProviderNamespaces, which defaults to allow-all (nil).\n\tif !isCrossProviderNamespaceAllowed(c.crossProviderNamespaces, parentNamespace) && strings.Contains(service.Name, providerNamespaceSeparator) {\n\t\treturn \"\", nil, fmt.Errorf(\"service %q reference is not allowed: ...\", service.Name)\n\t}\n\t// ^-- MISSING: no `!c.allowCrossNamespace && strings.HasSuffix(service.Name, \"@\"+ProviderName)` rejection.\n\n\tswitch service.Kind {\n\tcase \"TraefikService\":\n\t\treturn fullServiceName(svcCtx, service, intstr.FromInt(0)), nil, nil // 690: returns the cross-namespace reference\n\t...\n\t}\n}\n```\n\nFor comparison, the sibling resolver used for middleware and TLS references does carry the guard:\n\n```go\n// pkg/provider/kubernetes/crd/kubernetes.go:1653-1668 — resolveReference (CORRECT)\nfunc resolveReference(ctx context.Context, parentNs, ns, name string, crossProviderNamespaces []string, allowCrossNamespace bool) (string, error) {\n\tif strings.Contains(name, providerNamespaceSeparator) {\n\t\tif !allowCrossNamespace && strings.HasSuffix(name, providerNamespaceSeparator+ProviderName) {\n\t\t\treturn \"\", errors.New(\"when allowCrossNamespace is disabled, @kubernetescrd references are disallowed\") // 1656 — THE GUARD\n\t\t}\n\t\t...\n\t}\n\t...\n}\n```\n\nThe same guard is also present at `pkg/provider/kubernetes/crd/kubernetes_http.go:500` (`makeServersTransportKey`, HTTP) and `pkg/provider/kubernetes/crd/kubernetes_tcp.go:316` (`makeTCPServersTransportKey`, TCP, added by commit `67501cbe`). Only the service resolver `nameAndService` lacks it.\n\n### Data flow\n\nAn `IngressRoute` created by a tenant in namespace `attacker` declares a route service `{ name: \"victim-backend@kubernetescrd\", kind: TraefikService }`; the tenant controls this reference string. In `nameAndService`, because the name contains `@`, the same-namespace check at line 669 is skipped, and `isCrossProviderNamespaceAllowed(nil, \"attacker\")` returns `true` under the default `nil` allowlist, so no rejection fires. `fullServiceName` then resolves the reference to the victim namespace's `TraefikService`, and the attacker's HTTP router is generated and bound to the victim's backend. At runtime the attacker's `Host(...)` route forwards to namespace `victim`'s backend pods.\n\n### Default reachability\n\n`AllowCrossNamespace` defaults to `false` (`pkg/provider/kubernetes/crd/kubernetes.go:57`, never set to `true` by any `SetDefaults`), so the isolation this bug bypasses is on by default. `CrossProviderNamespaces` defaults to `nil`, and `isCrossProviderNamespaceAllowed` returns `true` for a `nil` allowlist (`pkg/provider/kubernetes/crd/kubernetes.go:1645-1651`), so the only check `nameAndService` applies to an `@`-name is inert by default. The attacker needs only namespace-scoped RBAC to create an `IngressRoute` or `TraefikService` in their own namespace (the standard hard-multi-tenant Traefik setup) and knowledge of the target `TraefikService`'s namespace and name.\n\n### PoC\nA table-style harness was added to the CRD provider package. It defines a victim `TraefikService` (`backend` in namespace `victim`, backed by a real endpoint) and an attacker `IngressRoute` (namespace `attacker`) that references it via `victim-backend@kubernetescrd`, plus a control route that references a victim `Middleware` via `victim-mw@kubernetescrd`. The control route is given a valid local service so that the only reason it could be dropped is the cross-namespace middleware guard. The provider is run with `AllowCrossNamespace: false` and `CrossProviderNamespaces: nil` (both defaults).\n\n```\n$ go test -run TestPoC_CrossNamespaceServiceBypass ./pkg/provider/kubernetes/crd/ -v\n\nHTTP routers:  [attacker-attacker-svc-route-7df4381938699bd21215]\nHTTP services: [victim-whoami-victim-80 victim-backend]\nCONTROL OK: cross-ns MIDDLEWARE ref (victim-mw@kubernetescrd) rejected -> router dropped\nBYPASS CONFIRMED: attacker router bound to cross-ns service \"victim-backend\" despite AllowCrossNamespace=false\n```\n\nThe control route (middleware reference) is dropped even though it has a valid local service, confirming that the isolation control is active for middlewares; the service route survives and its `Service` field resolves to `victim-backend`, with the victim's services pulled into the generated configuration and reachable through the attacker's router.\n\nThe harness also runs two corroborating cases. With `AllowCrossNamespace=false` and `CrossProviderNamespaces=[\"someotherns\"]` (an allowlist that excludes the attacker), the service reference is blocked, which proves that the only gate ever applied to an `@kubernetescrd` service name is `crossProviderNamespaces` (inert by default) and that `allowCrossNamespace=false` is never consulted. With `AllowCrossNamespace=true`, both the service and middleware references are accepted, as expected when isolation is intentionally disabled.\n\n### Impact\nIn a multi-tenant cluster relying on `allowCrossNamespace=false` for namespace isolation, a tenant confined to their own namespace can attach their own router (their own `Host` rule and entrypoint) to another tenant's `TraefikService` backend, exposing an otherwise internal-only service on the data plane under the attacker's hostname, and can route or mirror traffic to another namespace's backend that they should not be able to reference.\n\n\n</details>\n---","state":0,"publishedAt":"2026-08-06T16:38:37+00:00","modifiedAt":"2026-08-18T15:11:01.1912624+00:00","affected":[{"ecosystem":"Go","name":"github.com/traefik/traefik/v2","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"2.11.54"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"Go","name":"github.com/traefik/traefik/v3","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"3.0.0"},{"kind":"fixed","version":"3.6.25"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"Go","name":"github.com/traefik/traefik/v3","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"3.7.0"},{"kind":"fixed","version":"3.7.10"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"Go","name":"github.com/traefik/traefik","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"last_affected","version":"1.7.34"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/traefik/traefik/security/advisories/GHSA-62fc-8686-hfmq","https://github.com/traefik/traefik/commit/65ebf4b47fbdc33e3856803a5844a404e094d52d","https://github.com/traefik/traefik","https://github.com/traefik/traefik/releases/tag/v2.11.54","https://github.com/traefik/traefik/releases/tag/v3.6.25","https://github.com/traefik/traefik/releases/tag/v3.7.10"],"sourceUrl":"https://github.com/advisories/GHSA-62fc-8686-hfmq","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-62fc-8686-hfmq","identifiers":["GHSA-62fc-8686-hfmq","CVE-2026-71325","GO-2026-6203"]},"retained":false,"historicalAffected":[]},{"revision":"8b6d39026fce43f18029173ffbd002bf","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GO-2026-6203","aliases":["CVE-2026-71325","GHSA-62fc-8686-hfmq"],"title":"Traefik: `allowCrossNamespace=false` bypass via `@kubernetescrd` TraefikService backendRef in github.com/traefik/traefik","description":"Traefik: `allowCrossNamespace=false` bypass via `@kubernetescrd` TraefikService backendRef in github.com/traefik/traefik","state":0,"publishedAt":"2026-08-18T14:32:29+00:00","modifiedAt":"2026-08-18T15:00:24.5408738+00:00","affected":[{"ecosystem":"Go","name":"github.com/traefik/traefik","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"Go","name":"github.com/traefik/traefik/v2","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"2.11.54"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"Go","name":"github.com/traefik/traefik/v3","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"3.0.0"},{"kind":"fixed","version":"3.6.25"},{"kind":"introduced","version":"3.7.0"},{"kind":"fixed","version":"3.7.10"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://github.com/traefik/traefik/security/advisories/GHSA-62fc-8686-hfmq","https://github.com/traefik/traefik/commit/65ebf4b47fbdc33e3856803a5844a404e094d52d","https://github.com/traefik/traefik/releases/tag/v2.11.54","https://github.com/traefik/traefik/releases/tag/v3.6.25","https://github.com/traefik/traefik/releases/tag/v3.7.10"],"sourceUrl":"https://osv.dev/vulnerability/GO-2026-6203","license":"OSV · upstream source license applies","key":"osv:GO-2026-6203","identifiers":["GO-2026-6203","CVE-2026-71325","GHSA-62fc-8686-hfmq"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-13T09:56:58.0475153+00:00","complete":true,"records":1779,"lastAttemptAt":"2026-11-13T09:56:58.0475153+00:00","lastSuccessAt":"2026-11-13T09:56:58.2099581+00:00","error":null,"lastVerifiedAt":"2026-11-13T09:56:58.2099587+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-d8fa82e95fdb59244e2f635e667ba17f0796ca0a4f1f4bb8cc31febcd660b76c-34cd709e5a7980bd64603fef264386c6773edbeefa1003d00f6c892f1a82ba78","complete":true,"records":425015,"lastAttemptAt":"2026-11-13T09:56:57.738401+00:00","lastSuccessAt":"2026-11-13T09:56:57.6929119+00:00","error":null,"lastVerifiedAt":"2026-11-13T09:56:57.738401+00:00","snapshotPublishedAt":"2026-11-13T09:29:11+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-4189021905f4442a93afe149a0fe7218","complete":false,"records":13793,"lastAttemptAt":"2026-11-13T10:00:24.1261082+00:00","lastSuccessAt":"2026-11-13T10:00:24.1849444+00:00","error":null,"lastVerifiedAt":"2026-11-13T10:00:24.1849444+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-13T09:56:58.0475153+00:00","complete":true,"records":1123,"lastAttemptAt":"2026-11-13T09:56:58.0475153+00:00","lastSuccessAt":"2026-11-13T09:56:58.2109737+00:00","error":null,"lastVerifiedAt":"2026-11-13T09:56:58.2109738+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-4ba957c820134164a894230a688495c2","complete":true,"records":13793,"lastAttemptAt":"2026-11-13T09:56:59.8152537+00:00","lastSuccessAt":"2026-11-13T09:56:59.811+00:00","error":null,"lastVerifiedAt":"2026-11-13T09:56:59.811+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13846,"expectedIdentifiers":13846,"failedIdentifiers":0},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-93e76d404e1aeb6a7e8902f5ffa06211fc86dea3b1958e297abb2668aa5e6e8c","complete":true,"records":9952,"lastAttemptAt":"2026-11-13T09:56:58.0026399+00:00","lastSuccessAt":"2026-11-12T23:19:15.5239119+00:00","error":null,"lastVerifiedAt":"2026-11-13T09:56:58.0026399+00:00","snapshotPublishedAt":"2026-11-12T23:03:02+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-4d60731753a2f72e455d1086e7203d0ef10843936dcc1cf2b45135e2caa204b0","complete":true,"records":2012,"lastAttemptAt":"2026-11-13T09:56:57.7985974+00:00","lastSuccessAt":"2026-11-12T18:16:50.7862525+00:00","error":null,"lastVerifiedAt":"2026-11-13T09:56:57.7985974+00:00","snapshotPublishedAt":"2026-11-12T17:48:11+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-20d1a8ab073a1c13ab2143dbcadb34ebb8edf1e18e16482b448513662c3d1e12","complete":true,"records":3127,"lastAttemptAt":"2026-11-13T09:56:58.0153464+00:00","lastSuccessAt":"2026-11-12T22:18:31.0338213+00:00","error":null,"lastVerifiedAt":"2026-11-13T09:56:58.0153464+00:00","snapshotPublishedAt":"2026-11-12T22:18:06+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-24050939c62dd3b6b6239735dfea28a7170f2b40b5de29359847ee068e1ec8ff","complete":true,"records":231770,"lastAttemptAt":"2026-11-13T09:56:57.9057957+00:00","lastSuccessAt":"2026-11-13T08:59:14.8600113+00:00","error":null,"lastVerifiedAt":"2026-11-13T09:56:57.9057957+00:00","snapshotPublishedAt":"2026-11-13T08:32:55+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}