{
"document": {
"category": "csaf_base",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE"
}
},
"lang": "en",
"notes": [
{
"category": "legal_disclaimer",
"text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings."
}
],
"publisher": {
"category": "coordinator",
"contact_details": "cert@ncsc.nl",
"name": "National Cyber Security Centre",
"namespace": "https://www.ncsc.nl/"
},
"title": "CVE-2026-31801",
"tracking": {
"current_release_date": "2026-03-25T19:23:08.740704Z",
"generator": {
"date": "2026-02-17T15:00:00Z",
"engine": {
"name": "V.E.L.M.A",
"version": "1.7"
}
},
"id": "CVE-2026-31801",
"initial_release_date": "2026-03-10T21:30:13.979574Z",
"revision_history": [
{
"date": "2026-03-10T21:30:13.979574Z",
"number": "1",
"summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (1).| CWES updated (1)."
},
{
"date": "2026-03-10T21:30:19.991167Z",
"number": "2",
"summary": "NCSC Score created."
},
{
"date": "2026-03-10T21:40:18.247530Z",
"number": "3",
"summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (1).| References created (1).| CWES updated (1)."
},
{
"date": "2026-03-10T21:40:30.225988Z",
"number": "4",
"summary": "NCSC Score updated."
},
{
"date": "2026-03-11T00:53:26.639444Z",
"number": "5",
"summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (4).| CWES updated (1)."
},
{
"date": "2026-03-11T00:53:28.703077Z",
"number": "6",
"summary": "NCSC Score updated."
},
{
"date": "2026-03-11T14:54:36.990295Z",
"number": "7",
"summary": "Source created.| CVE status created. (valid)| EPSS created."
},
{
"date": "2026-03-11T14:54:40.522348Z",
"number": "8",
"summary": "NCSC Score updated."
},
{
"date": "2026-03-11T16:39:29.967955Z",
"number": "9",
"summary": "Unknown change."
},
{
"date": "2026-03-11T16:39:31.684151Z",
"number": "10",
"summary": "NCSC Score updated."
},
{
"date": "2026-03-18T20:25:04.066003Z",
"number": "11",
"summary": "Products created (1).| Product Identifiers created (1).| Exploits created (1)."
},
{
"date": "2026-03-18T20:25:06.281429Z",
"number": "12",
"summary": "NCSC Score updated."
},
{
"date": "2026-03-19T15:29:46.671685Z",
"number": "13",
"summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (4).| CWES updated (1)."
},
{
"date": "2026-03-19T15:29:49.299526Z",
"number": "14",
"summary": "NCSC Score updated."
},
{
"date": "2026-03-20T09:32:51.749648Z",
"number": "15",
"summary": "Source connected.| CVE status created. (valid)| EPSS created."
},
{
"date": "2026-03-25T18:14:22.298170Z",
"number": "16",
"summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (2).| References created (3).| CWES updated (1)."
},
{
"date": "2026-03-25T18:14:25.207345Z",
"number": "17",
"summary": "NCSC Score updated."
},
{
"date": "2026-03-25T18:15:06.037253Z",
"number": "18",
"summary": "Source created.| CVE status created. (valid)| Description created for source.| References created (3)."
},
{
"date": "2026-03-25T19:20:24.443528Z",
"number": "19",
"summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products connected (75).| Products created (12).| References created (3).| CWES updated (1)."
}
],
"status": "interim",
"version": "19"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "vers:unknown/>=0|<2.1.15",
"product": {
"name": "vers:unknown/>=0|<2.1.15",
"product_id": "CSAFPID-5907279"
}
},
{
"category": "product_version_range",
"name": "vers:unknown/>=1.3.0-20210831063041-c8779d9e87d9|<=1.4.4-20251014054906-73eef25681af",
"product": {
"name": "vers:unknown/>=1.3.0-20210831063041-c8779d9e87d9|<=1.4.4-20251014054906-73eef25681af",
"product_id": "CSAFPID-5907280"
}
},
{
"category": "product_version_range",
"name": "vers:unknown/>=1.3.0|=1.3.0|=1.3.0|<2.1.15",
"product": {
"name": "vers:unknown/>=1.3.0|<2.1.15",
"product_id": "CSAFPID-5845052",
"product_identification_helper": {
"cpe": "cpe:2.3:a:zotregistry:zot:*:*:*:*:*:*:*:*"
}
}
}
],
"category": "product_name",
"name": "zot"
}
],
"category": "vendor",
"name": "zotregistry"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2026-31801",
"cwe": {
"id": "CWE-863",
"name": "Incorrect Authorization"
},
"notes": [
{
"category": "description",
"text": "zot is ancontainer image/artifact registry based on the Open Container Initiative Distribution Specification. From 1.3.0 to 2.1.14, zot’s dist-spec authorization middleware infers the required action for PUT /v2/{name}/manifests/{reference} as create by default, and only switches to update when the tag already exists and reference != \"latest\". As a result, when latest already exists, a user who is allowed to create (but not allowed to update) can still pass the authorization check for an overwrite attempt of latest. This vulnerability is fixed in 2.1.15.",
"title": "nvd - https://nvd.nist.gov/vuln/detail/CVE-2026-31801"
},
{
"category": "description",
"text": "zot is ancontainer image/artifact registry based on the Open Container Initiative Distribution Specification. From 1.3.0 to 2.1.14, zot’s dist-spec authorization middleware infers the required action for PUT /v2/{name}/manifests/{reference} as create by default, and only switches to update when the tag already exists and reference != \"latest\". As a result, when latest already exists, a user who is allowed to create (but not allowed to update) can still pass the authorization check for an overwrite attempt of latest. This vulnerability is fixed in 2.1.15.",
"title": "cveprojectv5 - https://www.cve.org/CVERecord?id=CVE-2026-31801"
},
{
"category": "description",
"text": "zot’s dist-spec authorization middleware infers the required action for `PUT /v2/{name}/manifests/{reference}` as `create` by default, and only switches to `update` when the tag already exists and `reference != \"latest\"`.\n\nas a result, when `latest` already exists, a user who is allowed to `create` (but not allowed to `update`) can still pass the authorization check for an overwrite attempt of `latest`.\n\n## affected component\n\n- file: `pkg/api/authz.go` (`DistSpecAuthzHandler`)\n- condition: `slices.Contains(tags, reference) && reference != \"latest\"` (line 352 at the pinned commit)\n\n## severity\n\nHIGH\ncategory: CWE-863 (incorrect authorization)\n\nnote: impact depends on how a deployment uses `latest` (for example, if `latest` is treated as a protected or “push-once” tag), and on how access control is provisioned (users with `create` but without `update`). the attached poc demonstrates a real overwrite of `latest` (tag digest changes) under a create-only policy.\n\n## steps to reproduce\n\n1. configure access control so user `attacker` has `create` but not `update` on a repository.\n2. ensure the repository has an existing tag named `latest`.\n3. attempt to push a new manifest to `/v2/acme/app/manifests/latest` (example repository name).\n4. observe that the authorization check is evaluated as `create` (not `update`) for `latest`, so the request passes authorization even though the tag already exists.\n\nthe attached poc demonstrates this deterministically with `canonical.log` and `control.log` markers.\n\n## expected vs actual\n\n- expected: overwriting an existing tag should require `update` permission, including `latest` (or `latest` should be explicitly documented as exempt).\n- actual: when `reference==\"latest\"` and the tag exists, the middleware keeps the action as `create` instead of switching to `update`.\n\n## security impact\n\nthis can break least-privilege expectations in deployments that rely on the `create` vs `update` split to prevent tag overwrites (for example, “push-once” policies). if `latest` is used as a high-trust tag in ci/cd, this can create supply-chain risk because a create-only principal can overwrite an existing `latest` tag while other existing tags correctly require `update`.\n\n## suggested fix\n\nremove the special-case exemption for `latest` when determining whether an existing tag requires `update` permission (treat `latest` the same as other tags), or document and enforce an explicit policy rule for `latest`.\n\n## notes / rationale\n\n- oci distribution spec does not define a standard authorization model; this report is about zot’s own create vs update semantics and the observable behavior in `DistSpecAuthzHandler`.\n- zot documentation describes immutable tags as being enforceable via authorization policies (create-only “push once”, update disallowed). if `latest` is exempt, this control does not apply to `latest` unless documented otherwise.\n\n[addendum.md](https://github.com/user-attachments/files/24986139/addendum.md)\n[poc.zip](https://github.com/user-attachments/files/24986140/poc.zip)\n[PR_DESCRIPTION.md](https://github.com/user-attachments/files/24986141/PR_DESCRIPTION.md)\n[RUNNABLE_POC.md](https://github.com/user-attachments/files/24986142/RUNNABLE_POC.md)",
"title": "github - https://github.com/advisories/GHSA-85jx-fm8m-x8c6"
},
{
"category": "description",
"text": "zot’s dist-spec authorization middleware infers the required action for `PUT /v2/{name}/manifests/{reference}` as `create` by default, and only switches to `update` when the tag already exists and `reference != \"latest\"`.\n\nas a result, when `latest` already exists, a user who is allowed to `create` (but not allowed to `update`) can still pass the authorization check for an overwrite attempt of `latest`.\n\n## affected component\n\n- file: `pkg/api/authz.go` (`DistSpecAuthzHandler`)\n- condition: `slices.Contains(tags, reference) && reference != \"latest\"` (line 352 at the pinned commit)\n\n## severity\n\nHIGH\ncategory: CWE-863 (incorrect authorization)\n\nnote: impact depends on how a deployment uses `latest` (for example, if `latest` is treated as a protected or “push-once” tag), and on how access control is provisioned (users with `create` but without `update`). the attached poc demonstrates a real overwrite of `latest` (tag digest changes) under a create-only policy.\n\n## steps to reproduce\n\n1. configure access control so user `attacker` has `create` but not `update` on a repository.\n2. ensure the repository has an existing tag named `latest`.\n3. attempt to push a new manifest to `/v2/acme/app/manifests/latest` (example repository name).\n4. observe that the authorization check is evaluated as `create` (not `update`) for `latest`, so the request passes authorization even though the tag already exists.\n\nthe attached poc demonstrates this deterministically with `canonical.log` and `control.log` markers.\n\n## expected vs actual\n\n- expected: overwriting an existing tag should require `update` permission, including `latest` (or `latest` should be explicitly documented as exempt).\n- actual: when `reference==\"latest\"` and the tag exists, the middleware keeps the action as `create` instead of switching to `update`.\n\n## security impact\n\nthis can break least-privilege expectations in deployments that rely on the `create` vs `update` split to prevent tag overwrites (for example, “push-once” policies). if `latest` is used as a high-trust tag in ci/cd, this can create supply-chain risk because a create-only principal can overwrite an existing `latest` tag while other existing tags correctly require `update`.\n\n## suggested fix\n\nremove the special-case exemption for `latest` when determining whether an existing tag requires `update` permission (treat `latest` the same as other tags), or document and enforce an explicit policy rule for `latest`.\n\n## notes / rationale\n\n- oci distribution spec does not define a standard authorization model; this report is about zot’s own create vs update semantics and the observable behavior in `DistSpecAuthzHandler`.\n- zot documentation describes immutable tags as being enforceable via authorization policies (create-only “push once”, update disallowed). if `latest` is exempt, this control does not apply to `latest` unless documented otherwise.\n\n[addendum.md](https://github.com/user-attachments/files/24986139/addendum.md)\n[poc.zip](https://github.com/user-attachments/files/24986140/poc.zip)\n[PR_DESCRIPTION.md](https://github.com/user-attachments/files/24986141/PR_DESCRIPTION.md)\n[RUNNABLE_POC.md](https://github.com/user-attachments/files/24986142/RUNNABLE_POC.md)",
"title": "github - https://api.github.com/advisories/GHSA-85jx-fm8m-x8c6"
},
{
"category": "description",
"text": "zot’s dist-spec authorization middleware infers the required action for `PUT /v2/{name}/manifests/{reference}` as `create` by default, and only switches to `update` when the tag already exists and `reference != \"latest\"`.\n\nas a result, when `latest` already exists, a user who is allowed to `create` (but not allowed to `update`) can still pass the authorization check for an overwrite attempt of `latest`.\n\n## affected component\n\n- file: `pkg/api/authz.go` (`DistSpecAuthzHandler`)\n- condition: `slices.Contains(tags, reference) && reference != \"latest\"` (line 352 at the pinned commit)\n\n## severity\n\nHIGH\ncategory: CWE-863 (incorrect authorization)\n\nnote: impact depends on how a deployment uses `latest` (for example, if `latest` is treated as a protected or “push-once” tag), and on how access control is provisioned (users with `create` but without `update`). the attached poc demonstrates a real overwrite of `latest` (tag digest changes) under a create-only policy.\n\n## steps to reproduce\n\n1. configure access control so user `attacker` has `create` but not `update` on a repository.\n2. ensure the repository has an existing tag named `latest`.\n3. attempt to push a new manifest to `/v2/acme/app/manifests/latest` (example repository name).\n4. observe that the authorization check is evaluated as `create` (not `update`) for `latest`, so the request passes authorization even though the tag already exists.\n\nthe attached poc demonstrates this deterministically with `canonical.log` and `control.log` markers.\n\n## expected vs actual\n\n- expected: overwriting an existing tag should require `update` permission, including `latest` (or `latest` should be explicitly documented as exempt).\n- actual: when `reference==\"latest\"` and the tag exists, the middleware keeps the action as `create` instead of switching to `update`.\n\n## security impact\n\nthis can break least-privilege expectations in deployments that rely on the `create` vs `update` split to prevent tag overwrites (for example, “push-once” policies). if `latest` is used as a high-trust tag in ci/cd, this can create supply-chain risk because a create-only principal can overwrite an existing `latest` tag while other existing tags correctly require `update`.\n\n## suggested fix\n\nremove the special-case exemption for `latest` when determining whether an existing tag requires `update` permission (treat `latest` the same as other tags), or document and enforce an explicit policy rule for `latest`.\n\n## notes / rationale\n\n- oci distribution spec does not define a standard authorization model; this report is about zot’s own create vs update semantics and the observable behavior in `DistSpecAuthzHandler`.\n- zot documentation describes immutable tags as being enforceable via authorization policies (create-only “push once”, update disallowed). if `latest` is exempt, this control does not apply to `latest` unless documented otherwise.\n\n[addendum.md](https://github.com/user-attachments/files/24986139/addendum.md)\n[poc.zip](https://github.com/user-attachments/files/24986140/poc.zip)\n[PR_DESCRIPTION.md](https://github.com/user-attachments/files/24986141/PR_DESCRIPTION.md)\n[RUNNABLE_POC.md](https://github.com/user-attachments/files/24986142/RUNNABLE_POC.md)",
"title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGHSA-85jx-fm8m-x8c6.json?alt=media"
},
{
"category": "description",
"text": "zot’s create-only policy allows overwrite attempts of existing latest tag (update permission not required) in zotregistry.dev/zot.\n\nNOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.\n\n(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)\n\nThe additional affected modules and versions are: .",
"title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGO-2026-4668.json?alt=media"
},
{
"category": "description",
"text": "zot is ancontainer image/artifact registry based on the Open Container Initiative Distribution Specification. From 1.3.0 to 2.1.14, zot’s dist-spec authorization middleware infers the required action for PUT /v2/{name}/manifests/{reference} as create by default, and only switches to update when the tag already exists and reference != \"latest\". As a result, when latest already exists, a user who is allowed to create (but not allowed to update) can still pass the authorization check for an overwrite attempt of latest. This vulnerability is fixed in 2.1.15.",
"title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/GIT%2FCVE-2026-31801.json?alt=media"
},
{
"category": "other",
"text": "0.00033",
"title": "EPSS"
},
{
"category": "other",
"text": "3.4",
"title": "NCSC Score"
},
{
"category": "other",
"text": "Is related to (a version of) an uncommon product, Is related to an uncommon product vendor, There is exploit data available from source Nvd",
"title": "NCSC Score top decreasing factors"
}
],
"product_status": {
"known_affected": [
"CSAFPID-5778753",
"CSAFPID-5845052",
"CSAFPID-5907279",
"CSAFPID-5907280",
"CSAFPID-3637424",
"CSAFPID-3637425",
"CSAFPID-3637426",
"CSAFPID-3637427",
"CSAFPID-3637428",
"CSAFPID-3637429",
"CSAFPID-3637430",
"CSAFPID-3637431",
"CSAFPID-3637432",
"CSAFPID-3637433",
"CSAFPID-3637434",
"CSAFPID-3637435",
"CSAFPID-3637436",
"CSAFPID-3637437",
"CSAFPID-3637438",
"CSAFPID-3637439",
"CSAFPID-3637440",
"CSAFPID-3637441",
"CSAFPID-3637442",
"CSAFPID-3637443",
"CSAFPID-3637444",
"CSAFPID-3637445",
"CSAFPID-3637446",
"CSAFPID-3637447",
"CSAFPID-3637448",
"CSAFPID-3637449",
"CSAFPID-3637450",
"CSAFPID-3637451",
"CSAFPID-3637452",
"CSAFPID-3637453",
"CSAFPID-3637454",
"CSAFPID-3637455",
"CSAFPID-3637456",
"CSAFPID-3637457",
"CSAFPID-3637458",
"CSAFPID-3637459",
"CSAFPID-3637460",
"CSAFPID-3637461",
"CSAFPID-3637462",
"CSAFPID-3637463",
"CSAFPID-3637464",
"CSAFPID-3637465",
"CSAFPID-3637466",
"CSAFPID-3637467",
"CSAFPID-3637468",
"CSAFPID-3637469",
"CSAFPID-3637470",
"CSAFPID-3637471",
"CSAFPID-3637472",
"CSAFPID-3637473",
"CSAFPID-3637474",
"CSAFPID-3637475",
"CSAFPID-3637476",
"CSAFPID-3637477",
"CSAFPID-3637478",
"CSAFPID-3637479",
"CSAFPID-3637480",
"CSAFPID-3637481",
"CSAFPID-3637482",
"CSAFPID-3637483",
"CSAFPID-3637484",
"CSAFPID-3766888",
"CSAFPID-3766889",
"CSAFPID-3766890",
"CSAFPID-3766891",
"CSAFPID-3766892",
"CSAFPID-3766893",
"CSAFPID-3766894",
"CSAFPID-3766895",
"CSAFPID-3766896",
"CSAFPID-3766897",
"CSAFPID-3766898",
"CSAFPID-3766899",
"CSAFPID-3766900",
"CSAFPID-3766901",
"CSAFPID-5909380",
"CSAFPID-5909381",
"CSAFPID-5909382",
"CSAFPID-5909383",
"CSAFPID-5909384",
"CSAFPID-5909385",
"CSAFPID-5909386",
"CSAFPID-5909387",
"CSAFPID-5909388",
"CSAFPID-5909389",
"CSAFPID-5909390",
"CSAFPID-5909391"
]
},
"references": [
{
"category": "external",
"summary": "Source - nvd",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-31801"
},
{
"category": "external",
"summary": "Source raw - nvd",
"url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-31801"
},
{
"category": "external",
"summary": "Source - cveprojectv5",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-31801"
},
{
"category": "external",
"summary": "Source raw - cveprojectv5",
"url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/31xxx/CVE-2026-31801.json"
},
{
"category": "external",
"summary": "Source - github",
"url": "https://github.com/advisories/GHSA-85jx-fm8m-x8c6"
},
{
"category": "external",
"summary": "Source raw - github",
"url": "https://api.github.com/advisories/GHSA-85jx-fm8m-x8c6"
},
{
"category": "external",
"summary": "Source - first",
"url": "https://api.first.org/data/v1/epss?cve=CVE-2026-31801"
},
{
"category": "external",
"summary": "Source raw - first",
"url": "https://api.first.org/data/v1/epss?limit=10000&offset=0"
},
{
"category": "external",
"summary": "Source - github",
"url": "https://api.github.com/advisories/GHSA-85jx-fm8m-x8c6"
},
{
"category": "external",
"summary": "Source - first",
"url": "https://api.first.org/data/v1/epss?limit=10000&offset=0"
},
{
"category": "external",
"summary": "Source - osv",
"url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGHSA-85jx-fm8m-x8c6.json?alt=media"
},
{
"category": "external",
"summary": "Source - osv",
"url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGO-2026-4668.json?alt=media"
},
{
"category": "external",
"summary": "Source - osv",
"url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/GIT%2FCVE-2026-31801.json?alt=media"
},
{
"category": "external",
"summary": "Reference - cveprojectv5; github; nvd; osv",
"url": "https://github.com/project-zot/zot/security/advisories/GHSA-85jx-fm8m-x8c6"
},
{
"category": "external",
"summary": "Reference - github; osv",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-31801"
},
{
"category": "external",
"summary": "Reference - github; osv",
"url": "https://github.com/project-zot/zot/releases/tag/v2.1.15"
},
{
"category": "external",
"summary": "Reference - github",
"url": "https://github.com/advisories/GHSA-85jx-fm8m-x8c6"
},
{
"category": "external",
"summary": "Reference - osv",
"url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31801.json"
}
],
"scores": [
{
"cvss_v3": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N",
"baseScore": 7.7,
"baseSeverity": "HIGH"
},
"products": [
"CSAFPID-3637424",
"CSAFPID-3637425",
"CSAFPID-3637426",
"CSAFPID-3637427",
"CSAFPID-3637428",
"CSAFPID-3637429",
"CSAFPID-3637430",
"CSAFPID-3637431",
"CSAFPID-3637432",
"CSAFPID-3637433",
"CSAFPID-3637434",
"CSAFPID-3637435",
"CSAFPID-3637436",
"CSAFPID-3637437",
"CSAFPID-3637438",
"CSAFPID-3637439",
"CSAFPID-3637440",
"CSAFPID-3637441",
"CSAFPID-3637442",
"CSAFPID-3637443",
"CSAFPID-3637444",
"CSAFPID-3637445",
"CSAFPID-3637446",
"CSAFPID-3637447",
"CSAFPID-3637448",
"CSAFPID-3637449",
"CSAFPID-3637450",
"CSAFPID-3637451",
"CSAFPID-3637452",
"CSAFPID-3637453",
"CSAFPID-3637454",
"CSAFPID-3637455",
"CSAFPID-3637456",
"CSAFPID-3637457",
"CSAFPID-3637458",
"CSAFPID-3637459",
"CSAFPID-3637460",
"CSAFPID-3637461",
"CSAFPID-3637462",
"CSAFPID-3637463",
"CSAFPID-3637464",
"CSAFPID-3637465",
"CSAFPID-3637466",
"CSAFPID-3637467",
"CSAFPID-3637468",
"CSAFPID-3637469",
"CSAFPID-3637470",
"CSAFPID-3637471",
"CSAFPID-3637472",
"CSAFPID-3637473",
"CSAFPID-3637474",
"CSAFPID-3637475",
"CSAFPID-3637476",
"CSAFPID-3637477",
"CSAFPID-3637478",
"CSAFPID-3637479",
"CSAFPID-3637480",
"CSAFPID-3637481",
"CSAFPID-3637482",
"CSAFPID-3637483",
"CSAFPID-3637484",
"CSAFPID-3766888",
"CSAFPID-3766889",
"CSAFPID-3766890",
"CSAFPID-3766891",
"CSAFPID-3766892",
"CSAFPID-3766893",
"CSAFPID-3766894",
"CSAFPID-3766895",
"CSAFPID-3766896",
"CSAFPID-3766897",
"CSAFPID-3766898",
"CSAFPID-3766899",
"CSAFPID-3766900",
"CSAFPID-3766901",
"CSAFPID-5778753",
"CSAFPID-5845052",
"CSAFPID-5907279",
"CSAFPID-5907280",
"CSAFPID-5909380",
"CSAFPID-5909381",
"CSAFPID-5909382",
"CSAFPID-5909383",
"CSAFPID-5909384",
"CSAFPID-5909385",
"CSAFPID-5909386",
"CSAFPID-5909387",
"CSAFPID-5909388",
"CSAFPID-5909389",
"CSAFPID-5909390",
"CSAFPID-5909391"
]
}
],
"title": "CVE-2026-31801"
}
]
}