CVE-2026-132643 (GCVE-0-2026-132643)

Vulnerability from cvelistv5 – Published: 2026-11-18 21:08 – Updated: 2026-11-18 21:25
VLAI
Title
MISP Anonymised Sightings Reporter Identity Disclosure via Organisation Filter
Summary
MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter's organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation's ID in the filter. The query would then return only that organisation's sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
Supplier · CIRCL (v2.0.3)
Decision recorded 2026-11-18 21:06 UTC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-18 21:24 UTC
CWE
  • CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-862 - Missing Authorization
Assigner
CIRCL CNA under the ENISA root
CNA scorecard A 91/100 over 275 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
misp misp Affected: 0 , ≤ 2.5.51 (semver)
    cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*
Create a notification for this product.
GCVE extensions
bcp-05-x-01
AI-assisted vulnerability information annotation
GCVE-BCP-05-X-01
Whole record AI-generated Human-reviewed GNA-1

Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.

ai-computer-assisted:llm-generatedai-computer-assisted:classification
Model Source Identifier
qwen3.8:27b ollama qwen3.8:27b
bcp-05-x-02
Patch-to-vulnerability generation provenance
GCVE-BCP-05-X-02
Generator
patch2vuln.py on 2026-11-18 21:06
Model
qwen3.8:27b
Input
https://github.com/MISP/MISP/commit/415f07967.patch 0eacdfd112fc…
Confidence
medium
Commit Subject Patch SHA-256
415f07967704 fix: [security] Anonymised sightings cannot be attributed 0eacdfd112fc…
Fix summary

A new authorization check (orgFilterAllowed) is introduced in the Sighting model. When Sightings_anonymise is enabled, a non-site-admin user's org_id filter targeting another organisation is rejected: listSightings returns an empty result set, and restSearch either skips the negated condition or substitutes an impossible value (-1) for the positive filter. Site administrators and users filtering by their own organisation retain full functionality. When anonymization is disabled, the filter behaves as before.

Patch summary

Adds a private method orgFilterAllowed() to app/Model/Sighting.php that returns true only when anonymization is off, the user is a site admin, or the org_id matches the user's own organisation. In listSightings(), an early return of an empty array is inserted when the filter is not allowed. In restSearch(), when the filter is not allowed, negated conditions are skipped (continue) and positive conditions are set to org_id = -1 to match nothing. A new regression test class SightingsAnonymisedOrgFilter in tests/testregressions.py validates that non-admins cannot unmask reporters via either endpoint, that site admins retain filter access, and that the filter remains functional when anonymization is disabled.

CVSS rationale

AV:N: MISP is a network-accessible web application; the vulnerable endpoints are HTTP APIs. AC:L: Exploitation requires only adding an org_id parameter to a standard API call; no race conditions, timing, or complex setup needed. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with perm_sighting (sighting read) is sufficient; site admin is not required. UI:N: No victim interaction is needed; the attacker simply calls the API. VC:L: The impact is limited to revealing which organisation reported a sighting; full record contents and other data remain protected. VI:N, VA:N: No integrity or availability impact. SC:N, SI:N, SA:N: No impact on subsequent components or safety.

Weakness rationale
  • CWE-200 The primary impact is disclosure of the reporter's organisation identity, which the anonymization feature is designed to conceal. A non-privileged user can determine which organisation reported a sighting by filtering on that organisation's ID.
  • CWE-862 The root cause is the absence of an authorization check on the org_id filter parameter. The endpoint accepted and applied any caller-supplied organisation ID without verifying whether the requesting user was permitted to filter by that organisation, especially in the context of anonymized sightings.
Attack pattern rationale
  • CAPEC-66 The attacker manipulates the org_id request parameter to filter results by a specific organisation, thereby bypassing the anonymization control. This is the closest CAPEC to the observed attack: a legitimate parameter is used in a way that circumvents a security policy (anonymization). Uncertainty: this is not a classic parameter tampering (e.g., altering a price or ID to access another user's data) but rather exploiting a filter parameter to infer information that should be masked. No CAPEC specifically covers 'bypassing anonymization via filter parameter', so CAPEC-66 is the best available match.
Assumptions to verify
  • The Sightings_anonymise setting must be enabled for the vulnerability to be exploitable; when disabled, the org_id filter is expected behavior and not a vulnerability.
  • The user must have perm_sighting (sighting read permission) but must NOT be a site admin (perm_site_admin); site admins are explicitly allowed to filter by any organisation.
  • The affected version range is unknown; the patch does not specify a version boundary. All versions of MISP with the Sightings_anonymise feature and the pre-fix listSightings/restSearch code are assumed affected.
  • CAPEC-66 (Parameter Tampering) is the closest available attack pattern; no CAPEC specifically describes bypassing an anonymization control via a filter parameter, so this mapping carries uncertainty.
  • CVSS PR:L assumes the attacker needs only a standard authenticated MISP user account with sighting read permissions; the exact minimum role is inferred from the test setup (least_privileged_role with perm_add and perm_sighting).
  • The Co-Authored-By line references an AI assistant (Claude Opus 5.5); it is credited as a tool rather than a human remediation developer.
Model comparison

Selected qwen3.8:27b by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.

Model Score Agreement Confidence Assumptions
qwen3.8:27b 6 11 medium 6
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-11-09 13:31 UTC Fix developed Corrective change authored (415f07967704bbc83b1c7ff599c913b752581457): fix: [security] Anonymised sightings cannot be attributed https://github.com/MISP/MISP/commit/415f07967.patch
  2. 2026-11-18 21:05 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/415f07967.patch
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-132643",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-18T21:24:56.466463Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-18T21:25:04.425Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "Sighting model (app/Model/Sighting.php)",
            "listSightings endpoint",
            "sightings/restSearch endpoint"
          ],
          "product": "misp",
          "programFiles": [
            "app/Model/Sighting.php"
          ],
          "repo": "https://github.com/MISP/MISP",
          "vendor": "misp",
          "versions": [
            {
              "lessThanOrEqual": "2.5.51",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "2.5.51",
                  "versionStartIncluding": "0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "ENISA"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "iglocska"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Claude Opus 5.5"
        },
        {
          "lang": "en",
          "type": "tool",
          "value": "Claude Opus 5.5"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter\u0027s organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation\u0027s ID in the filter. The query would then return only that organisation\u0027s sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-66",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-66 Parameter Tampering"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "format": "SSVC",
          "other": {
            "content": {
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "yes"
                },
                {
                  "Technical Impact": "partial"
                }
              ],
              "role": "Supplier",
              "timestamp": "2026-11-18T21:06:20Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "CWE-200 Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-862",
              "description": "CWE-862 Missing Authorization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-18T21:08:37.441Z",
        "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "shortName": "CIRCL"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/MISP/MISP/commit/415f07967"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "A new authorization check (orgFilterAllowed) is introduced in the Sighting model. When Sightings_anonymise is enabled, a non-site-admin user\u0027s org_id filter targeting another organisation is rejected: listSightings returns an empty result set, and restSearch either skips the negated condition or substitutes an impossible value (-1) for the positive filter. Site administrators and users filtering by their own organisation retain full functionality. When anonymization is disabled, the filter behaves as before."
        }
      ],
      "title": "MISP Anonymised Sightings Reporter Identity Disclosure via Organisation Filter",
      "x_gcve": [
        {
          "extensions": {
            "bcp-05-x-01": {
              "ai_annotations": [
                {
                  "ai_level": "generated",
                  "description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
                  "gna_source": 1,
                  "models": [
                    {
                      "gna_source": 1,
                      "identifier": "qwen3.8:27b",
                      "name": "qwen3.8:27b",
                      "source": "ollama"
                    }
                  ],
                  "review_status": "full",
                  "scope": "record",
                  "tags": [
                    "ai-computer-assisted:llm-generated",
                    "ai-computer-assisted:classification"
                  ]
                }
              ]
            },
            "bcp-05-x-02": {
              "x_patch2vuln": {
                "assumptions": [
                  "The Sightings_anonymise setting must be enabled for the vulnerability to be exploitable; when disabled, the org_id filter is expected behavior and not a vulnerability.",
                  "The user must have perm_sighting (sighting read permission) but must NOT be a site admin (perm_site_admin); site admins are explicitly allowed to filter by any organisation.",
                  "The affected version range is unknown; the patch does not specify a version boundary. All versions of MISP with the Sightings_anonymise feature and the pre-fix listSightings/restSearch code are assumed affected.",
                  "CAPEC-66 (Parameter Tampering) is the closest available attack pattern; no CAPEC specifically describes bypassing an anonymization control via a filter parameter, so this mapping carries uncertainty.",
                  "CVSS PR:L assumes the attacker needs only a standard authenticated MISP user account with sighting read permissions; the exact minimum role is inferred from the test setup (least_privileged_role with perm_add and perm_sighting).",
                  "The Co-Authored-By line references an AI assistant (Claude Opus 5.5); it is credited as a tool rather than a human remediation developer."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-66",
                    "rationale": "The attacker manipulates the org_id request parameter to filter results by a specific organisation, thereby bypassing the anonymization control. This is the closest CAPEC to the observed attack: a legitimate parameter is used in a way that circumvents a security policy (anonymization). Uncertainty: this is not a classic parameter tampering (e.g., altering a price or ID to access another user\u0027s data) but rather exploiting a filter parameter to infer information that should be masked. No CAPEC specifically covers \u0027bypassing anonymization via filter parameter\u0027, so CAPEC-66 is the best available match."
                  }
                ],
                "commit": "415f07967704bbc83b1c7ff599c913b752581457",
                "confidence": "medium",
                "credits": [
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "ENISA"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "iglocska"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "Claude Opus 5.5"
                  },
                  {
                    "lang": "en",
                    "type": "tool",
                    "value": "Claude Opus 5.5"
                  }
                ],
                "cvssRationale": "AV:N: MISP is a network-accessible web application; the vulnerable endpoints are HTTP APIs. AC:L: Exploitation requires only adding an org_id parameter to a standard API call; no race conditions, timing, or complex setup needed. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with perm_sighting (sighting read) is sufficient; site admin is not required. UI:N: No victim interaction is needed; the attacker simply calls the API. VC:L: The impact is limited to revealing which organisation reported a sighting; full record contents and other data remain protected. VI:N, VA:N: No integrity or availability impact. SC:N, SI:N, SA:N: No impact on subsequent components or safety.",
                "draft": false,
                "fixSummary": "A new authorization check (orgFilterAllowed) is introduced in the Sighting model. When Sightings_anonymise is enabled, a non-site-admin user\u0027s org_id filter targeting another organisation is rejected: listSightings returns an empty result set, and restSearch either skips the negated condition or substitutes an impossible value (-1) for the positive filter. Site administrators and users filtering by their own organisation retain full functionality. When anonymization is disabled, the filter behaves as before.",
                "generatedAt": "2026-11-18T21:06:20.520780Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 6,
                      "confidence": "medium",
                      "model": "qwen3.8:27b",
                      "score": 6
                    }
                  ],
                  "selectedModel": "qwen3.8:27b",
                  "selectionMethod": "deterministic-consensus-v1",
                  "selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
                },
                "patchSha256": "0eacdfd112fcbdac0e7bc2baacaaaec68d1bc5dc84f466b7adc8b54f695234e9",
                "patchSummary": "Adds a private method orgFilterAllowed() to app/Model/Sighting.php that returns true only when anonymization is off, the user is a site admin, or the org_id matches the user\u0027s own organisation. In listSightings(), an early return of an empty array is inserted when the filter is not allowed. In restSearch(), when the filter is not allowed, negated conditions are skipped (continue) and positive conditions are set to org_id = -1 to match nothing. A new regression test class SightingsAnonymisedOrgFilter in tests/testregressions.py validates that non-admins cannot unmask reporters via either endpoint, that site admins retain filter access, and that the filter remains functional when anonymization is disabled.",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "415f07967704bbc83b1c7ff599c913b752581457",
                    "date": "Mon, 9 Nov 2026 14:31:56 +0100",
                    "patchSha256": "0eacdfd112fcbdac0e7bc2baacaaaec68d1bc5dc84f466b7adc8b54f695234e9",
                    "retrievedAt": "2026-11-18T21:05:44.744740Z",
                    "source": "https://github.com/MISP/MISP/commit/415f07967.patch",
                    "sourceUrl": "https://github.com/MISP/MISP/commit/415f07967.patch",
                    "subject": "fix: [security] Anonymised sightings cannot be attributed"
                  }
                ],
                "source": "https://github.com/MISP/MISP/commit/415f07967.patch",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-18T21:06:20Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] Anonymised sightings cannot be attributed",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-200",
                    "rationale": "The primary impact is disclosure of the reporter\u0027s organisation identity, which the anonymization feature is designed to conceal. A non-privileged user can determine which organisation reported a sighting by filtering on that organisation\u0027s ID."
                  },
                  {
                    "cweId": "CWE-862",
                    "rationale": "The root cause is the absence of an authorization check on the org_id filter parameter. The endpoint accepted and applied any caller-supplied organisation ID without verifying whether the requesting user was permitted to filter by that organisation, especially in the context of anonymized sightings."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "description": "Corrective change authored (415f07967704bbc83b1c7ff599c913b752581457): fix: [security] Anonymised sightings cannot be attributed",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/MISP/MISP/commit/415f07967.patch"
                    ],
                    "timestamp": "2026-11-09T13:31:56Z",
                    "type": "fix-developed"
                  },
                  {
                    "description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
                    "id": "evt-fix-available-1",
                    "references": [
                      "https://github.com/MISP/MISP/commit/415f07967.patch"
                    ],
                    "timestamp": "2026-11-18T21:05:44.744740Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "gcve-1-2026-20282"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
    "assignerShortName": "CIRCL",
    "cveId": "CVE-2026-132643",
    "datePublished": "2026-11-18T21:08:37.441Z",
    "dateReserved": "2026-11-18T21:08:33.062Z",
    "dateUpdated": "2026-11-18T21:25:04.425Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-132643",
      "date": "2026-11-19",
      "epss": "0.00344",
      "percentile": "0.28521"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "cpes": [
                  "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
                ],
                "modules": [
                  "Sighting model (app/Model/Sighting.php)",
                  "listSightings endpoint",
                  "sightings/restSearch endpoint"
                ],
                "product": "misp",
                "programFiles": [
                  "app/Model/Sighting.php"
                ],
                "repo": "https://github.com/MISP/MISP",
                "vendor": "misp",
                "versions": [
                  {
                    "lessThanOrEqual": "2.5.51",
                    "status": "affected",
                    "version": "0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter\u0027s organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation\u0027s ID in the filter. The query would then return only that organisation\u0027s sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA."
          }
        ],
        "id": "CVE-2026-132643",
        "lastModified": "2026-11-18T22:17:21.407",
        "metrics": {
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "NONE",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "NOT_DEFINED",
                "privilegesRequired": "LOW",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/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",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "LOW",
                "vulnIntegrityImpact": "NONE",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
              "ssvcData": {
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "yes"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "Supplier",
                "timestamp": "2026-11-18T21:06:20Z",
                "version": "2.0.3"
              }
            },
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-132643",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-18T21:24:56.466463Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-11-18T21:17:58.547",
        "references": [
          {
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
            "url": "https://github.com/MISP/MISP/commit/415f07967"
          }
        ],
        "sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "vulnStatus": "Deferred",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-200"
              },
              {
                "lang": "en",
                "value": "CWE-862"
              }
            ],
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
            "type": "Secondary"
          }
        ]
      }
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-132643",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-11-18T21:24:56.466463Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-11-18T21:24:59.785Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "cpes": [
                "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
              ],
              "modules": [
                "Sighting model (app/Model/Sighting.php)",
                "listSightings endpoint",
                "sightings/restSearch endpoint"
              ],
              "product": "misp",
              "programFiles": [
                "app/Model/Sighting.php"
              ],
              "repo": "https://github.com/MISP/MISP",
              "vendor": "misp",
              "versions": [
                {
                  "lessThanOrEqual": "2.5.51",
                  "status": "affected",
                  "version": "0",
                  "versionType": "semver"
                }
              ]
            }
          ],
          "cpeApplicability": [
            {
              "nodes": [
                {
                  "cpeMatch": [
                    {
                      "criteria": "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "2.5.51",
                      "versionStartIncluding": "0",
                      "vulnerable": true
                    }
                  ],
                  "negate": false,
                  "operator": "OR"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "ENISA"
            },
            {
              "lang": "en",
              "type": "remediation developer",
              "value": "iglocska"
            },
            {
              "lang": "en",
              "type": "remediation developer",
              "value": "Claude Opus 5.5"
            },
            {
              "lang": "en",
              "type": "tool",
              "value": "Claude Opus 5.5"
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter\u0027s organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation\u0027s ID in the filter. The query would then return only that organisation\u0027s sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA."
            }
          ],
          "impacts": [
            {
              "capecId": "CAPEC-66",
              "descriptions": [
                {
                  "lang": "en",
                  "value": "CAPEC-66 Parameter Tampering"
                }
              ]
            }
          ],
          "metrics": [
            {
              "cvssV4_0": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "NONE",
                "attackVector": "NETWORK",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "privilegesRequired": "LOW",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "LOW",
                "vulnIntegrityImpact": "NONE",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            },
            {
              "format": "SSVC",
              "other": {
                "content": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-18T21:06:20Z",
                  "version": "2.0.3"
                },
                "type": "SSVC"
              },
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-200",
                  "description": "CWE-200 Exposure of Sensitive Information to an Unauthorized Actor",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "cweId": "CWE-862",
                  "description": "CWE-862 Missing Authorization",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-11-18T21:08:37.441Z",
            "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
            "shortName": "CIRCL"
          },
          "references": [
            {
              "name": "Security patch",
              "tags": [
                "patch"
              ],
              "url": "https://github.com/MISP/MISP/commit/415f07967"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "A new authorization check (orgFilterAllowed) is introduced in the Sighting model. When Sightings_anonymise is enabled, a non-site-admin user\u0027s org_id filter targeting another organisation is rejected: listSightings returns an empty result set, and restSearch either skips the negated condition or substitutes an impossible value (-1) for the positive filter. Site administrators and users filtering by their own organisation retain full functionality. When anonymization is disabled, the filter behaves as before."
            }
          ],
          "title": "MISP Anonymised Sightings Reporter Identity Disclosure via Organisation Filter",
          "x_gcve": [
            {
              "extensions": {
                "bcp-05-x-01": {
                  "ai_annotations": [
                    {
                      "ai_level": "generated",
                      "description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
                      "gna_source": 1,
                      "models": [
                        {
                          "gna_source": 1,
                          "identifier": "qwen3.8:27b",
                          "name": "qwen3.8:27b",
                          "source": "ollama"
                        }
                      ],
                      "review_status": "full",
                      "scope": "record",
                      "tags": [
                        "ai-computer-assisted:llm-generated",
                        "ai-computer-assisted:classification"
                      ]
                    }
                  ]
                },
                "bcp-05-x-02": {
                  "x_patch2vuln": {
                    "assumptions": [
                      "The Sightings_anonymise setting must be enabled for the vulnerability to be exploitable; when disabled, the org_id filter is expected behavior and not a vulnerability.",
                      "The user must have perm_sighting (sighting read permission) but must NOT be a site admin (perm_site_admin); site admins are explicitly allowed to filter by any organisation.",
                      "The affected version range is unknown; the patch does not specify a version boundary. All versions of MISP with the Sightings_anonymise feature and the pre-fix listSightings/restSearch code are assumed affected.",
                      "CAPEC-66 (Parameter Tampering) is the closest available attack pattern; no CAPEC specifically describes bypassing an anonymization control via a filter parameter, so this mapping carries uncertainty.",
                      "CVSS PR:L assumes the attacker needs only a standard authenticated MISP user account with sighting read permissions; the exact minimum role is inferred from the test setup (least_privileged_role with perm_add and perm_sighting).",
                      "The Co-Authored-By line references an AI assistant (Claude Opus 5.5); it is credited as a tool rather than a human remediation developer."
                    ],
                    "capecRationale": [
                      {
                        "capecId": "CAPEC-66",
                        "rationale": "The attacker manipulates the org_id request parameter to filter results by a specific organisation, thereby bypassing the anonymization control. This is the closest CAPEC to the observed attack: a legitimate parameter is used in a way that circumvents a security policy (anonymization). Uncertainty: this is not a classic parameter tampering (e.g., altering a price or ID to access another user\u0027s data) but rather exploiting a filter parameter to infer information that should be masked. No CAPEC specifically covers \u0027bypassing anonymization via filter parameter\u0027, so CAPEC-66 is the best available match."
                      }
                    ],
                    "commit": "415f07967704bbc83b1c7ff599c913b752581457",
                    "confidence": "medium",
                    "credits": [
                      {
                        "lang": "en",
                        "type": "reporter",
                        "value": "ENISA"
                      },
                      {
                        "lang": "en",
                        "type": "remediation developer",
                        "value": "iglocska"
                      },
                      {
                        "lang": "en",
                        "type": "remediation developer",
                        "value": "Claude Opus 5.5"
                      },
                      {
                        "lang": "en",
                        "type": "tool",
                        "value": "Claude Opus 5.5"
                      }
                    ],
                    "cvssRationale": "AV:N: MISP is a network-accessible web application; the vulnerable endpoints are HTTP APIs. AC:L: Exploitation requires only adding an org_id parameter to a standard API call; no race conditions, timing, or complex setup needed. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with perm_sighting (sighting read) is sufficient; site admin is not required. UI:N: No victim interaction is needed; the attacker simply calls the API. VC:L: The impact is limited to revealing which organisation reported a sighting; full record contents and other data remain protected. VI:N, VA:N: No integrity or availability impact. SC:N, SI:N, SA:N: No impact on subsequent components or safety.",
                    "draft": false,
                    "fixSummary": "A new authorization check (orgFilterAllowed) is introduced in the Sighting model. When Sightings_anonymise is enabled, a non-site-admin user\u0027s org_id filter targeting another organisation is rejected: listSightings returns an empty result set, and restSearch either skips the negated condition or substitutes an impossible value (-1) for the positive filter. Site administrators and users filtering by their own organisation retain full functionality. When anonymization is disabled, the filter behaves as before.",
                    "generatedAt": "2026-11-18T21:06:20.520780Z",
                    "generator": "patch2vuln.py",
                    "model": "qwen3.8:27b",
                    "modelComparison": {
                      "potentialErrors": [],
                      "rankings": [
                        {
                          "agreementScore": 11,
                          "assumptionCount": 6,
                          "confidence": "medium",
                          "model": "qwen3.8:27b",
                          "score": 6
                        }
                      ],
                      "selectedModel": "qwen3.8:27b",
                      "selectionMethod": "deterministic-consensus-v1",
                      "selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
                    },
                    "patchSha256": "0eacdfd112fcbdac0e7bc2baacaaaec68d1bc5dc84f466b7adc8b54f695234e9",
                    "patchSummary": "Adds a private method orgFilterAllowed() to app/Model/Sighting.php that returns true only when anonymization is off, the user is a site admin, or the org_id matches the user\u0027s own organisation. In listSightings(), an early return of an empty array is inserted when the filter is not allowed. In restSearch(), when the filter is not allowed, negated conditions are skipped (continue) and positive conditions are set to org_id = -1 to match nothing. A new regression test class SightingsAnonymisedOrgFilter in tests/testregressions.py validates that non-admins cannot unmask reporters via either endpoint, that site admins retain filter access, and that the filter remains functional when anonymization is disabled.",
                    "patchTruncated": false,
                    "patches": [
                      {
                        "commit": "415f07967704bbc83b1c7ff599c913b752581457",
                        "date": "Mon, 9 Nov 2026 14:31:56 +0100",
                        "patchSha256": "0eacdfd112fcbdac0e7bc2baacaaaec68d1bc5dc84f466b7adc8b54f695234e9",
                        "retrievedAt": "2026-11-18T21:05:44.744740Z",
                        "source": "https://github.com/MISP/MISP/commit/415f07967.patch",
                        "sourceUrl": "https://github.com/MISP/MISP/commit/415f07967.patch",
                        "subject": "fix: [security] Anonymised sightings cannot be attributed"
                      }
                    ],
                    "source": "https://github.com/MISP/MISP/commit/415f07967.patch",
                    "ssvc": {
                      "options": [
                        {
                          "Exploitation": "none"
                        },
                        {
                          "Automatable": "yes"
                        },
                        {
                          "Technical Impact": "partial"
                        }
                      ],
                      "role": "Supplier",
                      "timestamp": "2026-11-18T21:06:20Z",
                      "version": "2.0.3"
                    },
                    "subject": "fix: [security] Anonymised sightings cannot be attributed",
                    "weaknessRationale": [
                      {
                        "cweId": "CWE-200",
                        "rationale": "The primary impact is disclosure of the reporter\u0027s organisation identity, which the anonymization feature is designed to conceal. A non-privileged user can determine which organisation reported a sighting by filtering on that organisation\u0027s ID."
                      },
                      {
                        "cweId": "CWE-862",
                        "rationale": "The root cause is the absence of an authorization check on the org_id filter parameter. The endpoint accepted and applied any caller-supplied organisation ID without verifying whether the requesting user was permitted to filter by that organisation, especially in the context of anonymized sightings."
                      }
                    ]
                  }
                },
                "bcp-05-x-03": {
                  "x_timeline": {
                    "events": [
                      {
                        "description": "Corrective change authored (415f07967704bbc83b1c7ff599c913b752581457): fix: [security] Anonymised sightings cannot be attributed",
                        "id": "evt-fix-developed-1",
                        "references": [
                          "https://github.com/MISP/MISP/commit/415f07967.patch"
                        ],
                        "timestamp": "2026-11-09T13:31:56Z",
                        "type": "fix-developed"
                      },
                      {
                        "description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
                        "id": "evt-fix-available-1",
                        "references": [
                          "https://github.com/MISP/MISP/commit/415f07967.patch"
                        ],
                        "timestamp": "2026-11-18T21:05:44.744740Z",
                        "type": "fix-available"
                      }
                    ]
                  }
                }
              },
              "recordType": "advisory",
              "vulnId": "gcve-1-2026-20282"
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "assignerShortName": "CIRCL",
        "cveId": "CVE-2026-132643",
        "datePublished": "2026-11-18T21:08:37.441Z",
        "dateReserved": "2026-11-18T21:08:33.062Z",
        "dateUpdated": "2026-11-18T21:25:04.425Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Solutions

CNA · CIRCL
A new authorization check (orgFilterAllowed) is introduced in the Sighting model. When Sightings_anonymise is enabled, a non-site-admin user's org_id filter targeting another organisation is rejected: listSightings returns an empty result set, and restSearch either skips the negated condition or substitutes an impossible value (-1) for the positive filter. Site administrators and users filtering by their own organisation retain full functionality. When anonymization is disabled, the filter behaves as before.

Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.