CWE-639
Weakness AllowedAuthorization Bypass Through User-Controlled Key
Abstraction: Base · Status: Incomplete
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
It is likely that an attacker would have to be an authenticated user in the system. However, the authorization process would not properly check the data access operation to ensure that the authenticated user performing the operation has sufficient entitlements to perform the requested data access, hence bypassing any other authorization checks present in the system.
For example, attackers can look at places where user specific data is retrieved (e.g. search screens) and determine whether the key for the item being looked up is controllable externally. The key may be a hidden field in the HTML form field, might be passed as a URL parameter or as an unencrypted cookie variable, then in each of these cases it will be possible to tamper with the key value.
Mapping guidance
This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Relationships and members
Modes of introduction
REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Retrieval of a user record occurs in the system based on some key value that is under user control. The key would typically identify a user-related record stored in the system and would be used to lookup that record for presentation to the user.
One manifestation of this weakness is when a system uses sequential or otherwise easily-guessable session IDs that would allow one user to easily switch to another user's session and read/modify their data.
Detection methods
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Effectiveness: High
Notes
Maintenance
As of CWE 4.20, the relationship between IDOR and BOLA needs to be investigated more closely, including research into how these terms are used in the industry. The CWE team suspects that IDOR can be a part of BOLA, but BOLA expands on the weakness inherent to IDOR in that it is not only about objects that are being directly referenced.
Content history
Suggested corrections to use of IDOR versus BOLA
updated Common_Consequences, Relationships, Type
updated Description
updated Relationships
updated Relationships
updated Common_Consequences
updated Relationships
updated Alternate_Terms, Applicable_Platforms, Description, Name, Potential_Mitigations, Relationships
updated Common_Consequences, Relationships
updated Relationships
updated Alternate_Terms, Common_Consequences
updated Relationships
updated Relationships
updated Description, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Relationships
updated Relationships
updated Relationships
updated Relationships
updated Alternate_Terms
updated Relationships
updated Alternate_Terms
updated Relationships
updated Detection_Factors, Relationships
updated Mapping_Notes
updated Observed_Examples
updated Demonstrative_Examples
updated References, Relationships, Weakness_Ordinalities
updated Alternate_Terms, Maintenance_Notes, References
updated Description, Modes_of_Introduction, Time_of_Introduction
6021 vulnerabilities reference this CWE, most recent first.
GCVE-1337-2026-000000000… (CVE-2026-105040)
Vulnerability from gna-1337 – Published: 2026-10-15 20:43 – Updated: 2026-10-15 20:43 Exclusively Hosted Service- CWE-639 - Authorization Bypass Through User-Controlled Key
| URL | Tags |
|---|---|
| https://github.com/xn0tsa/your-secrets-are-safe-with-me | technical-description |
| https://takeonme.org/gcves/GCVE-1337-2026-0000000… | third-party-advisory |
| https://www.theverge.com/tech/1010727/eiliko-robo… | media-coverage |
| Vendor | Product | Version | |
|---|---|---|---|
| EnergizeLab | NestJS auth service |
Affected:
1.8.2
|
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "NestJS auth service",
"vendor": "EnergizeLab",
"versions": [
{
"status": "affected",
"version": "1.8.2"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Sammy Azdoufal"
},
{
"lang": "en",
"type": "coordinator",
"value": "todb of AHA!"
}
],
"datePublic": "2026-10-15T12:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "The EnergizeLab Eilik NestJS auth service accepts a user-controlled user ID in account update requests (mass assignment). A registered user can set another account\u0027s identifier and take over that account."
}
],
"value": "The EnergizeLab Eilik NestJS auth service accepts a user-controlled user ID in account update requests (mass assignment). A registered user can set another account\u0027s identifier and take over that account."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"other": {
"content": {
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CNA",
"version": "2.0.3"
},
"type": "ssvc"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-639",
"description": "CWE-639 Authorization Bypass Through User-Controlled Key",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-15T20:43:47.669Z",
"orgId": "26969f82-7e87-44d8-9cb5-f6fb926ddd43",
"shortName": "AHA"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://github.com/xn0tsa/your-secrets-are-safe-with-me"
},
{
"tags": [
"third-party-advisory"
],
"url": "https://takeonme.org/gcves/GCVE-1337-2026-00000000000000011111111111111111111000000000000000000011111101001111111110000000000000000000011111111111111111111000000000000010100/"
},
{
"tags": [
"media-coverage"
],
"url": "https://www.theverge.com/tech/1010727/eiliko-robot-hack-energize-lab"
}
],
"source": {
"discovery": "EXTERNAL"
},
"tags": [
"exclusively-hosted-service"
],
"title": "EnergizeLab Eilik User-ID Mass Assignment Account Takeover",
"x_gcve": [
{
"recordType": "advisory",
"vulnId": "gcve-1337-2026-00000000000000011111111111111111111000000000000000000011111101001111111110000000000000000000011111111111111111111000000000000010100"
}
],
"x_generator": {
"engine": "Vulnogram 1.0.2"
}
}
},
"cveMetadata": {
"assignerOrgId": "26969f82-7e87-44d8-9cb5-f6fb926ddd43",
"assignerShortName": "AHA",
"cveId": "CVE-2026-105040",
"datePublished": "2026-10-15T20:43:47.669Z",
"dateReserved": "2026-10-02T21:30:55.242Z",
"dateUpdated": "2026-10-15T20:43:47.669Z",
"serial": 1,
"state": "PUBLISHED",
"vulnId": "GCVE-1337-2026-00000000000000011111111111111111111000000000000000000011111101001111111110000000000000000000011111111111111111111000000000000010100"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-132774 (GCVE-0-2026-132774)
Vulnerability from cvelistv5 – Published: 2026-11-18 23:12 – Updated: 2026-11-18 23:12- CWE-639 - Authorization Bypass Through User-Controlled Key
| URL | Tags |
|---|---|
| https://github.com/Attendize/Attendize/issues/1154 | issue-tracking |
| https://github.com/Attendize/Attendize/blob/9289a… | technical-description |
| https://www.vulncheck.com/advisories/attendize-th… | third-party-advisory |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:github/attendize/attendize",
"product": "Attendize",
"repo": "https://github.com/Attendize/Attendize",
"vendor": "Attendize",
"versions": [
{
"lessThanOrEqual": "2.8.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "lighthousekeeper1212"
},
{
"lang": "en",
"type": "finder",
"value": "Boymirza Rejavaliyev (phantom)"
}
],
"datePublic": "2026-02-24T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Attendize through 2.8.0 contains a cross-account authorization bypass vulnerability in EventAttendeesController::postMessageAttendees() that allows authenticated organisers to message other accounts\u0027 attendees by supplying a foreign event_id. Attackers, including self-registered organisers, can post to the attendees message endpoint for another event to send arbitrary emails to all attendees, enabling phishing and impersonation."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-639",
"description": "Authorization Bypass Through User-Controlled Key",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T23:12:48.837Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"tags": [
"issue-tracking"
],
"url": "https://github.com/Attendize/Attendize/issues/1154"
},
{
"tags": [
"technical-description"
],
"url": "https://github.com/Attendize/Attendize/blob/9289acbab1583898fd85aeee66c7b613d8971deb/app/Http/Controllers/EventAttendeesController.php#L406-L432"
},
{
"name": "VulnCheck Advisory: Attendize through 2.8.0 Authorization Bypass via postMessageAttendees",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/attendize-through-2.8.0-authorization-bypass-via-postmessageattendees"
}
],
"title": "Attendize through 2.8.0 Authorization Bypass via postMessageAttendees",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-132774",
"datePublished": "2026-11-18T23:12:48.837Z",
"dateReserved": "2026-11-18T22:45:24.320Z",
"dateUpdated": "2026-11-18T23:12:48.837Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-132773 (GCVE-0-2026-132773)
Vulnerability from cvelistv5 – Published: 2026-11-18 23:12 – Updated: 2026-11-18 23:12- CWE-639 - Authorization Bypass Through User-Controlled Key
| URL | Tags |
|---|---|
| https://github.com/Attendize/Attendize/issues/1154 | issue-tracking |
| https://github.com/Attendize/Attendize/issues/1156 | issue-tracking |
| https://github.com/Attendize/Attendize/blob/9289a… | technical-description |
| https://github.com/Attendize/Attendize/blob/9289a… | technical-description |
| https://www.vulncheck.com/advisories/attendize-th… | third-party-advisory |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:github/attendize/attendize",
"product": "Attendize",
"repo": "https://github.com/Attendize/Attendize",
"vendor": "Attendize",
"versions": [
{
"lessThanOrEqual": "2.8.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "lighthousekeeper1212"
},
{
"lang": "en",
"type": "finder",
"value": "Boymirza Rejavaliyev (phantom)"
}
],
"datePublic": "2026-02-24T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Attendize through 2.8.0 contains an authorization bypass vulnerability in EventOrdersController::postCancelOrder() that allows authenticated organisers to cancel attendees belonging to other accounts\u0027 events. Attackers can cancel one of their own orders while supplying foreign attendee IDs, which Attendee::findFromSelection() loads unfiltered, invalidating tickets for any event on the installation."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"privilegesRequired": "LOW",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "LOW",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "HIGH"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-639",
"description": "Authorization Bypass Through User-Controlled Key",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T23:12:49.534Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"tags": [
"issue-tracking"
],
"url": "https://github.com/Attendize/Attendize/issues/1154"
},
{
"tags": [
"issue-tracking"
],
"url": "https://github.com/Attendize/Attendize/issues/1156"
},
{
"tags": [
"technical-description"
],
"url": "https://github.com/Attendize/Attendize/blob/9289acbab1583898fd85aeee66c7b613d8971deb/app/Http/Controllers/EventOrdersController.php#L206-L226"
},
{
"tags": [
"technical-description"
],
"url": "https://github.com/Attendize/Attendize/blob/9289acbab1583898fd85aeee66c7b613d8971deb/app/Models/Attendee.php#L66-L69"
},
{
"name": "VulnCheck Advisory: Attendize through 2.8.0 Authorization Bypass via postCancelOrder",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/attendize-through-2.8.0-authorization-bypass-via-postcancelorder"
}
],
"title": "Attendize through 2.8.0 Authorization Bypass via postCancelOrder",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-132773",
"datePublished": "2026-11-18T23:12:49.534Z",
"dateReserved": "2026-11-18T22:45:23.969Z",
"dateUpdated": "2026-11-18T23:12:49.534Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-132645 (GCVE-0-2026-132645)
Vulnerability from cvelistv5 – Published: 2026-11-18 21:19 – Updated: 2026-11-18 21:29| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/fc1ce99a6 | patch |
qwen3.8:27b
2 events
advisory
bcp-05-x-01bcp-05-x-02bcp-05-x-03
Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.
| Model | Source | Identifier |
|---|---|---|
| qwen3.8:27b | ollama | qwen3.8:27b |
- Generator
-
patch2vuln.pyon 2026-11-18 21:15 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/fc1ce99a6.patch
5be467cde9c7… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
fc1ce99a660b
|
fix: [security] Galaxy imports no longer rewrite default or | 5be467cde9c7… |
Fix summary
The fix introduces an object-level authorization check (__mayUpdateCapturedGalaxy) that enforces three rules before any existing galaxy record is modified: default galaxies are never updatable via import or sync; non-default galaxies may only be updated by a site admin, the owning organization, or a sync user who has visibility on the record. The role-level permission check is moved before the captureOrganisationAndSG() call so that no organization or sharing-group data is captured for an unauthorized user. When an update is permitted, the org_id, orgc_id, and default fields are explicitly excluded from the write, preventing ownership transfer or default-flag demotion even by authorized updaters.
Patch summary
In app/Model/Galaxy.php: (1) a new private method __mayUpdateCapturedGalaxy() is added, returning false for default galaxies, true for site admins or same-org users, and true for sync users only if the galaxy passes the user's visibility conditions; (2) the existing-galaxy lookup and the __mayUpdateCapturedGalaxy() gate are moved before the captureOrganisationAndSG() call, so unauthorized users are rejected before any org/SG capture; (3) the role permission check (perm_site_admin / perm_galaxy_editor) is moved to the top of the method, before any data mutation; (4) when an existing galaxy is updated, org_id, orgc_id, and default are unset from the existing record before the field-diff loop, ensuring they are never overwritten; (5) a regression test suite (GalaxyCaptureUpdateGate in tests/testregressions.py) is added covering: other-org editor cannot update visible or hidden galaxies, owner can update own galaxy, sync user can update visible but not hidden galaxies, site admin can update without taking over, a
CVSS rationale
AV:N: MISP is a network-accessible web application. AC:L: The attacker only needs to submit a valid import payload with a matching UUID; no race conditions or special timing are required. AT:N: No attack-target manipulation is needed. PR:L: The attacker must be an authenticated user with the perm_galaxy_editor role (a low-privilege role in MISP). UI:N: No victim interaction is required; the import is a server-side operation. VC:N: No confidentiality impact is evident from the patch. VI:H: Integrity of galaxy records is severely compromised: ownership (org_id, orgc_id) is transferred and the default flag is cleared, corrupting shared threat-intelligence metadata. VA:L: Demoting default galaxies may degrade the instance's threat-intelligence functionality for all users, but the service remains operational. SC:N: No secondary confidentiality impact. SI:H: Secondary integrity impact extends to other organizations' galaxy data and the shared default galaxy set. SA:N: No secondary availability impact beyond the primary VA.
Weakness rationale
- CWE-862 The captureGalaxy() method performed only a coarse role-level check (perm_galaxy_editor) without verifying object-level ownership or the default-galaxy status of the target record. Any user with the editor role could overwrite galaxies belonging to other organizations or system default galaxies, which is a missing object-level authorization control.
- CWE-639 The attacker-supplied UUID in the import payload was used as the sole key to locate and overwrite an existing galaxy record. Because no ownership or default-status check was applied to the matched record, a user-controlled key (UUID) effectively bypassed the intended authorization boundary. This is a secondary, more specific manifestation of the missing authorization.
Attack pattern rationale
- CAPEC-114 The attacker crafts a galaxy import payload whose UUID field is set to match an existing galaxy (default or another organization's), thereby targeting a specific record for unauthorized modification. The UUID is a user-controlled parameter that the application used to identify the target object without sufficient authorization validation. This is the closest CAPEC pattern: the attacker tampers with a request parameter (UUID) to redirect the application's write operation to an unintended object. Uncertainty: CAPEC-114 is a broad pattern; a more specific 'authorization bypass' CAPEC does not exist in the catalog, so this is the best available match.
Assumptions to verify
- The affected MISP version range is not specified in the patch; the vulnerability is assumed to affect all versions containing the vulnerable captureGalaxy() logic prior to this commit.
- The perm_galaxy_editor role is assumed to be a low-privilege role available to non-admin users; if it is restricted to admins only, the PR metric would be H rather than L.
- The CAPEC-114 mapping is the closest available pattern; no CAPEC specifically covers 'authorization bypass via object-level key matching in a CRUD operation', so Parameter Tampering is used as the best approximation.
- The CVSS VA:L rating assumes that demoting default galaxies degrades but does not fully break instance functionality; if default galaxies are critical for core operations, VA could be H.
- The SSVC technical_impact of 'partial' assumes the integrity compromise does not cascade into a full loss of trust in the MISP instance's data; if downstream consumers rely on galaxy ownership for access control, the impact could be 'total'.
- The patch does not specify whether the vulnerability is exploitable via the sync/pull path ($fromPull=true) in addition to the manual import path; both paths share the same captureGalaxy() code and are assumed equally affected.
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 |
- 2026-11-11 00:25 UTC Fix developed Corrective change authored (fc1ce99a660b6f34e936b1947167de6748c11ecd): fix: [security] Galaxy imports no longer rewrite default or https://github.com/MISP/MISP/commit/fc1ce99a6.patch
- 2026-11-18 21:15 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/fc1ce99a6.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-132645",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T21:27:26.410941Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T21:29:19.314Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"Galaxy model (app/Model/Galaxy.php)",
"Galaxy import/sync endpoint"
],
"product": "misp",
"programFiles": [
"app/Model/Galaxy.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:*:*:*:*:*:*:*:*",
"versionEndIncluding": "2.5.51",
"versionStartIncluding": "0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "reporter",
"value": "CERT.pl"
},
{
"lang": "en",
"type": "tool",
"value": "Claude Opus 5.5"
}
],
"descriptions": [
{
"lang": "en",
"value": "MISP contains an authorization bypass vulnerability in the Galaxy import/sync functionality (captureGalaxy in app/Model/Galaxy.php). The captureGalaxy() method matched an incoming galaxy payload to an existing galaxy by UUID and unconditionally overwrote the matched record, regardless of whether the importing user belonged to the owning organization or whether the galaxy was a system-provided default galaxy. Any authenticated user holding the perm_galaxy_editor role could therefore: (1) demote a default galaxy by setting its default flag to false, (2) reassign the galaxy\u0027s org_id and orgc_id to the attacker\u0027s organization, effectively taking ownership, and (3) modify other galaxy fields (name, description, distribution, version). Additionally, the role-level permission check (perm_site_admin or perm_galaxy_editor) was executed after the captureOrganisationAndSG() call, meaning organization and sharing-group data was already captured before the authorization decision was made. The vulnerability requires an authenticated user with the perm_galaxy_editor role and the ability to submit a galaxy import payload containing a UUID that matches an existing galaxy. The security impact is loss of data integrity across the MISP instance: default galaxy definitions are corrupted, cross-organization ownership is silently transferred, and the integrity of shared threat-intelligence galaxy metadata is compromised for all users of the instance."
}
],
"impacts": [
{
"capecId": "CAPEC-114",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-114 Parameter Tampering"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "HIGH",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:H/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "LOW",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "HIGH",
"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:15:52Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-862",
"description": "CWE-862 Missing Authorization",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-639",
"description": "CWE-639 Authorization Bypass Through User-Controlled Key",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T21:19:09.816Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/fc1ce99a6"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix introduces an object-level authorization check (__mayUpdateCapturedGalaxy) that enforces three rules before any existing galaxy record is modified: default galaxies are never updatable via import or sync; non-default galaxies may only be updated by a site admin, the owning organization, or a sync user who has visibility on the record. The role-level permission check is moved before the captureOrganisationAndSG() call so that no organization or sharing-group data is captured for an unauthorized user. When an update is permitted, the org_id, orgc_id, and default fields are explicitly excluded from the write, preventing ownership transfer or default-flag demotion even by authorized updaters."
}
],
"title": "MISP Galaxy Import Authorization Bypass Allows Unauthorized Overwrite of Default and Other Organizations\u0027 Galaxies",
"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 affected MISP version range is not specified in the patch; the vulnerability is assumed to affect all versions containing the vulnerable captureGalaxy() logic prior to this commit.",
"The perm_galaxy_editor role is assumed to be a low-privilege role available to non-admin users; if it is restricted to admins only, the PR metric would be H rather than L.",
"The CAPEC-114 mapping is the closest available pattern; no CAPEC specifically covers \u0027authorization bypass via object-level key matching in a CRUD operation\u0027, so Parameter Tampering is used as the best approximation.",
"The CVSS VA:L rating assumes that demoting default galaxies degrades but does not fully break instance functionality; if default galaxies are critical for core operations, VA could be H.",
"The SSVC technical_impact of \u0027partial\u0027 assumes the integrity compromise does not cascade into a full loss of trust in the MISP instance\u0027s data; if downstream consumers rely on galaxy ownership for access control, the impact could be \u0027total\u0027.",
"The patch does not specify whether the vulnerability is exploitable via the sync/pull path ($fromPull=true) in addition to the manual import path; both paths share the same captureGalaxy() code and are assumed equally affected."
],
"capecRationale": [
{
"capecId": "CAPEC-114",
"rationale": "The attacker crafts a galaxy import payload whose UUID field is set to match an existing galaxy (default or another organization\u0027s), thereby targeting a specific record for unauthorized modification. The UUID is a user-controlled parameter that the application used to identify the target object without sufficient authorization validation. This is the closest CAPEC pattern: the attacker tampers with a request parameter (UUID) to redirect the application\u0027s write operation to an unintended object. Uncertainty: CAPEC-114 is a broad pattern; a more specific \u0027authorization bypass\u0027 CAPEC does not exist in the catalog, so this is the best available match."
}
],
"commit": "fc1ce99a660b6f34e936b1947167de6748c11ecd",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA and CERT.pl"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "reporter",
"value": "CERT.pl"
},
{
"lang": "en",
"type": "tool",
"value": "Claude Opus 5.5"
}
],
"cvssRationale": "AV:N: MISP is a network-accessible web application. AC:L: The attacker only needs to submit a valid import payload with a matching UUID; no race conditions or special timing are required. AT:N: No attack-target manipulation is needed. PR:L: The attacker must be an authenticated user with the perm_galaxy_editor role (a low-privilege role in MISP). UI:N: No victim interaction is required; the import is a server-side operation. VC:N: No confidentiality impact is evident from the patch. VI:H: Integrity of galaxy records is severely compromised: ownership (org_id, orgc_id) is transferred and the default flag is cleared, corrupting shared threat-intelligence metadata. VA:L: Demoting default galaxies may degrade the instance\u0027s threat-intelligence functionality for all users, but the service remains operational. SC:N: No secondary confidentiality impact. SI:H: Secondary integrity impact extends to other organizations\u0027 galaxy data and the shared default galaxy set. SA:N: No secondary availability impact beyond the primary VA.",
"draft": false,
"fixSummary": "The fix introduces an object-level authorization check (__mayUpdateCapturedGalaxy) that enforces three rules before any existing galaxy record is modified: default galaxies are never updatable via import or sync; non-default galaxies may only be updated by a site admin, the owning organization, or a sync user who has visibility on the record. The role-level permission check is moved before the captureOrganisationAndSG() call so that no organization or sharing-group data is captured for an unauthorized user. When an update is permitted, the org_id, orgc_id, and default fields are explicitly excluded from the write, preventing ownership transfer or default-flag demotion even by authorized updaters.",
"generatedAt": "2026-11-18T21:15:52.163729Z",
"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": "5be467cde9c75941feeb588d6c7c4cbb4dd901fcef21e7d0ab0d0429bc7c860d",
"patchSummary": "In app/Model/Galaxy.php: (1) a new private method __mayUpdateCapturedGalaxy() is added, returning false for default galaxies, true for site admins or same-org users, and true for sync users only if the galaxy passes the user\u0027s visibility conditions; (2) the existing-galaxy lookup and the __mayUpdateCapturedGalaxy() gate are moved before the captureOrganisationAndSG() call, so unauthorized users are rejected before any org/SG capture; (3) the role permission check (perm_site_admin / perm_galaxy_editor) is moved to the top of the method, before any data mutation; (4) when an existing galaxy is updated, org_id, orgc_id, and default are unset from the existing record before the field-diff loop, ensuring they are never overwritten; (5) a regression test suite (GalaxyCaptureUpdateGate in tests/testregressions.py) is added covering: other-org editor cannot update visible or hidden galaxies, owner can update own galaxy, sync user can update visible but not hidden galaxies, site admin can update without taking over, a",
"patchTruncated": false,
"patches": [
{
"commit": "fc1ce99a660b6f34e936b1947167de6748c11ecd",
"date": "Wed, 11 Nov 2026 01:25:24 +0100",
"patchSha256": "5be467cde9c75941feeb588d6c7c4cbb4dd901fcef21e7d0ab0d0429bc7c860d",
"retrievedAt": "2026-11-18T21:15:09.098816Z",
"source": "https://github.com/MISP/MISP/commit/fc1ce99a6.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/fc1ce99a6.patch",
"subject": "fix: [security] Galaxy imports no longer rewrite default or"
}
],
"source": "https://github.com/MISP/MISP/commit/fc1ce99a6.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T21:15:52Z",
"version": "2.0.3"
},
"subject": "fix: [security] Galaxy imports no longer rewrite default or",
"weaknessRationale": [
{
"cweId": "CWE-862",
"rationale": "The captureGalaxy() method performed only a coarse role-level check (perm_galaxy_editor) without verifying object-level ownership or the default-galaxy status of the target record. Any user with the editor role could overwrite galaxies belonging to other organizations or system default galaxies, which is a missing object-level authorization control."
},
{
"cweId": "CWE-639",
"rationale": "The attacker-supplied UUID in the import payload was used as the sole key to locate and overwrite an existing galaxy record. Because no ownership or default-status check was applied to the matched record, a user-controlled key (UUID) effectively bypassed the intended authorization boundary. This is a secondary, more specific manifestation of the missing authorization."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (fc1ce99a660b6f34e936b1947167de6748c11ecd): fix: [security] Galaxy imports no longer rewrite default or",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/fc1ce99a6.patch"
],
"timestamp": "2026-11-11T00:25:24Z",
"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/fc1ce99a6.patch"
],
"timestamp": "2026-11-18T21:15:09.098816Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20358"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-132645",
"datePublished": "2026-11-18T21:19:09.816Z",
"dateReserved": "2026-11-18T21:19:05.634Z",
"dateUpdated": "2026-11-18T21:29:19.314Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-132644 (GCVE-0-2026-132644)
Vulnerability from cvelistv5 – Published: 2026-11-18 21:13 – Updated: 2026-11-18 21:24| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/4ac836afd | patch |
qwen3.8:27b
2 events
advisory
bcp-05-x-01bcp-05-x-02bcp-05-x-03
Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.
| Model | Source | Identifier |
|---|---|---|
| qwen3.8:27b | ollama | qwen3.8:27b |
- Generator
-
patch2vuln.pyon 2026-11-18 21:10 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/4ac836afd.patch
7d89e603fc49… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
4ac836afde4a
|
fix: [security] Galaxy cluster imports no longer take over | 7d89e603fc49… |
Fix summary
The fix adds an authorization check (__mayUpdateCapturedCluster) before any update to an existing Galaxy Cluster, permitting the operation only for the cluster's owner organization, a sync user with visibility to the cluster, or a site administrator. It also introduces a CAPTURE_FIELDS allow-list applied via CakePHP's fieldList option on save(), which restricts writable fields and explicitly excludes org_id and orgc_id from the update path, preventing ownership transfer. The captureOrganisationAndSG() call is moved after the authorization check so that a rejected request cannot alter ownership.
Patch summary
In app/Model/GalaxyCluster.php: (1) Added a private const CAPTURE_FIELDS array listing the only fields captureCluster() may write, excluding the 'default' field. (2) Moved the existingGalaxyCluster lookup and the locked-cluster check before the captureOrganisationAndSG() call. (3) Added a call to the new __mayUpdateCapturedCluster() method that enforces owner-org, sync-user-visibility, or site-admin authorization. (4) Changed both save() calls to use ['fieldList' => self::CAPTURE_FIELDS]; the update path further removes org_id and orgc_id from the field list. (5) Added the __mayUpdateCapturedCluster() private method implementing the three-way authorization check. In tests/testregressions.py: added a GalaxyClusterCaptureUpdateGate test class with six test cases covering cross-org refusal, owner acceptance, sync-user visibility gating, and ownership preservation.
CVSS rationale
AV:N: MISP is a network-accessible web application; the import endpoint is reachable over HTTP. AC:L: The attacker needs only a valid galaxy-editor account and a target cluster UUID (discoverable via API enumeration or prior knowledge); no race condition or special timing is required. AT:N: No manipulation of the attack target is needed. PR:L: The attacker requires an authenticated account with the perm_galaxy_editor role, which is a non-trivial but not administrative privilege. UI:N: No victim interaction is required; the import is a server-side API call. VC:N: The primary impact is on integrity of cluster data and ownership; while an attacker could read cluster fields in error responses, the vulnerability is not a confidentiality bypass. VI:H: The attacker can overwrite cluster content (value, description, distribution, etc.) and transfer ownership (org_id, orgc_id) of clusters belonging to other organizations, severely compromising data integrity. VA:N: No denial-of-service impact is evident. SC:N: No impact on connected or downstream systems is demonstrated. SI:H: The integrity of shared threat-intelligence data across the MISP instance is compromised, affecting all consumers of the affected clusters. SA:N: No impact on the security posture of other systems.
Weakness rationale
- CWE-862 The captureCluster() update path performed no check that the requesting user was authorized to modify the specific cluster identified by UUID. Any user with the galaxy editor role could update and take ownership of clusters belonging to other organizations. The authorization logic was entirely absent for the cross-organization case.
- CWE-639 The cluster UUID, supplied by the attacker in the import payload, was used as the sole key to identify the target row for update without verifying that the caller had a legitimate relationship (ownership, sharing-group visibility, or admin role) to that specific resource.
Attack pattern rationale
- CAPEC-114 The attacker manipulates the UUID parameter in the galaxies/import request to target a specific Galaxy Cluster belonging to another organization. The system uses this user-supplied identifier to locate and overwrite the target row without validating the caller's authorization over that resource. This is the closest CAPEC to the observed attack: a legitimate API parameter (UUID) is used to redirect the operation to an unauthorized target. Uncertainty: CAPEC-114 typically describes tampering with multiple parameters or injecting unexpected values; here the parameter value is a valid UUID, and the core flaw is the missing authorization check rather than the parameter itself. However, no CAPEC more precisely captures 'using a valid resource identifier to perform an unauthorized operation on that resource,' making CAPEC-114 the best available match.
Assumptions to verify
- The affected MISP version range is not specified in the patch; the vulnerability is assumed to affect all versions containing the pre-fix captureCluster() implementation.
- The galaxy editor role (perm_galaxy_editor) is assumed to be a non-administrative, non-trivial permission that can be granted to multiple organizations on a shared MISP instance.
- CVSS VC is rated None because the primary demonstrated impact is integrity (modification and ownership transfer); any incidental confidentiality exposure via error messages is not the core vulnerability.
- CAPEC-114 (Parameter Tampering) is the closest available mapping; the core flaw is missing authorization rather than parameter manipulation per se, but no CAPEC more precisely describes 'using a valid resource identifier to perform an unauthorized operation.'
- The 'default' field exclusion from CAPTURE_FIELDS is noted in the commit message but its specific security significance is not further detailed in the patch; it is assumed to prevent modification of a cluster's default/flag status.
- 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.
- No specific MISP release version is identified as the first fixed version; the commit date (2026-11-10) is the only temporal anchor available.
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 |
5 | 11 | medium | 7 |
- 2026-11-10 16:49 UTC Fix developed Corrective change authored (4ac836afde4a29a90cd19322f6fb75a6940fb731): fix: [security] Galaxy cluster imports no longer take over https://github.com/MISP/MISP/commit/4ac836afd.patch
- 2026-11-18 21:09 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/4ac836afd.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-132644",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T21:24:15.022183Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T21:24:21.209Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"GalaxyCluster model (app/Model/GalaxyCluster.php)",
"Galaxy import/sync endpoint (galaxies/import)"
],
"product": "misp",
"programFiles": [
"app/Model/GalaxyCluster.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:*:*:*:*:*:*:*:*",
"versionEndIncluding": "2.5.51",
"versionStartIncluding": "0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA and CERT.pl"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "reporter",
"value": "CERT.pl"
},
{
"lang": "en",
"type": "tool",
"value": "Claude Opus 5.5"
}
],
"descriptions": [
{
"lang": "en",
"value": "MISP contains an authorization flaw in the GalaxyCluster model\u0027s captureCluster() function, which handles the import and synchronization of Galaxy Clusters. Prior to the fix, any authenticated user holding the galaxy editor role could replace an existing locked Galaxy Cluster by supplying its UUID in an import request, regardless of which organization owned the cluster. The function unconditionally called captureOrganisationAndSG() before the save operation, overwriting the cluster\u0027s org_id and orgc_id fields with the importing user\u0027s organization, effectively transferring ownership of the cluster to the attacker\u0027s organization. Additionally, the save operation was not restricted to a specific set of fields, allowing arbitrary field modification.\n\nThe vulnerable behavior required the attacker to possess a valid MISP account with the perm_galaxy_editor role and to know or discover the UUID of a target cluster belonging to another organization. No site-admin or owner-organization privilege was enforced for the update path. The result was that a low-privilege galaxy editor in one organization could modify the content (value, description, distribution, etc.) of clusters owned by other organizations and seize ownership, corrupting the integrity of shared threat-intelligence data across the MISP instance.\n\nThe vulnerability was reported by ENISA and CERT.pl. The fix introduces an explicit authorization gate that restricts cluster updates to the owner organization, a sync user who can see the cluster via sharing-group rules, or a site administrator, and enforces a field allow-list that excludes org_id and orgc_id from update writes, preserving original ownership."
}
],
"impacts": [
{
"capecId": "CAPEC-114",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-114 Parameter Tampering"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "HIGH",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:H/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T21:10:16Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-862",
"description": "CWE-862 Missing Authorization",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-639",
"description": "CWE-639 Authorization Bypass Through User-Controlled Key",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T21:13:49.544Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/4ac836afd"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix adds an authorization check (__mayUpdateCapturedCluster) before any update to an existing Galaxy Cluster, permitting the operation only for the cluster\u0027s owner organization, a sync user with visibility to the cluster, or a site administrator. It also introduces a CAPTURE_FIELDS allow-list applied via CakePHP\u0027s fieldList option on save(), which restricts writable fields and explicitly excludes org_id and orgc_id from the update path, preventing ownership transfer. The captureOrganisationAndSG() call is moved after the authorization check so that a rejected request cannot alter ownership."
}
],
"title": "MISP Galaxy Cluster Import Authorization Bypass Allows Cross-Organization Cluster Takeover",
"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 affected MISP version range is not specified in the patch; the vulnerability is assumed to affect all versions containing the pre-fix captureCluster() implementation.",
"The galaxy editor role (perm_galaxy_editor) is assumed to be a non-administrative, non-trivial permission that can be granted to multiple organizations on a shared MISP instance.",
"CVSS VC is rated None because the primary demonstrated impact is integrity (modification and ownership transfer); any incidental confidentiality exposure via error messages is not the core vulnerability.",
"CAPEC-114 (Parameter Tampering) is the closest available mapping; the core flaw is missing authorization rather than parameter manipulation per se, but no CAPEC more precisely describes \u0027using a valid resource identifier to perform an unauthorized operation.\u0027",
"The \u0027default\u0027 field exclusion from CAPTURE_FIELDS is noted in the commit message but its specific security significance is not further detailed in the patch; it is assumed to prevent modification of a cluster\u0027s default/flag status.",
"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.",
"No specific MISP release version is identified as the first fixed version; the commit date (2026-11-10) is the only temporal anchor available."
],
"capecRationale": [
{
"capecId": "CAPEC-114",
"rationale": "The attacker manipulates the UUID parameter in the galaxies/import request to target a specific Galaxy Cluster belonging to another organization. The system uses this user-supplied identifier to locate and overwrite the target row without validating the caller\u0027s authorization over that resource. This is the closest CAPEC to the observed attack: a legitimate API parameter (UUID) is used to redirect the operation to an unauthorized target. Uncertainty: CAPEC-114 typically describes tampering with multiple parameters or injecting unexpected values; here the parameter value is a valid UUID, and the core flaw is the missing authorization check rather than the parameter itself. However, no CAPEC more precisely captures \u0027using a valid resource identifier to perform an unauthorized operation on that resource,\u0027 making CAPEC-114 the best available match."
}
],
"commit": "4ac836afde4a29a90cd19322f6fb75a6940fb731",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA and CERT.pl"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "reporter",
"value": "CERT.pl"
},
{
"lang": "en",
"type": "tool",
"value": "Claude Opus 5.5"
}
],
"cvssRationale": "AV:N: MISP is a network-accessible web application; the import endpoint is reachable over HTTP. AC:L: The attacker needs only a valid galaxy-editor account and a target cluster UUID (discoverable via API enumeration or prior knowledge); no race condition or special timing is required. AT:N: No manipulation of the attack target is needed. PR:L: The attacker requires an authenticated account with the perm_galaxy_editor role, which is a non-trivial but not administrative privilege. UI:N: No victim interaction is required; the import is a server-side API call. VC:N: The primary impact is on integrity of cluster data and ownership; while an attacker could read cluster fields in error responses, the vulnerability is not a confidentiality bypass. VI:H: The attacker can overwrite cluster content (value, description, distribution, etc.) and transfer ownership (org_id, orgc_id) of clusters belonging to other organizations, severely compromising data integrity. VA:N: No denial-of-service impact is evident. SC:N: No impact on connected or downstream systems is demonstrated. SI:H: The integrity of shared threat-intelligence data across the MISP instance is compromised, affecting all consumers of the affected clusters. SA:N: No impact on the security posture of other systems.",
"draft": false,
"fixSummary": "The fix adds an authorization check (__mayUpdateCapturedCluster) before any update to an existing Galaxy Cluster, permitting the operation only for the cluster\u0027s owner organization, a sync user with visibility to the cluster, or a site administrator. It also introduces a CAPTURE_FIELDS allow-list applied via CakePHP\u0027s fieldList option on save(), which restricts writable fields and explicitly excludes org_id and orgc_id from the update path, preventing ownership transfer. The captureOrganisationAndSG() call is moved after the authorization check so that a rejected request cannot alter ownership.",
"generatedAt": "2026-11-18T21:10:16.939944Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 7,
"confidence": "medium",
"model": "qwen3.8:27b",
"score": 5
}
],
"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": "7d89e603fc49aaccca3169da87afdcc8fe49cdf1a05aa2aa6108ffe188f61c39",
"patchSummary": "In app/Model/GalaxyCluster.php: (1) Added a private const CAPTURE_FIELDS array listing the only fields captureCluster() may write, excluding the \u0027default\u0027 field. (2) Moved the existingGalaxyCluster lookup and the locked-cluster check before the captureOrganisationAndSG() call. (3) Added a call to the new __mayUpdateCapturedCluster() method that enforces owner-org, sync-user-visibility, or site-admin authorization. (4) Changed both save() calls to use [\u0027fieldList\u0027 =\u003e self::CAPTURE_FIELDS]; the update path further removes org_id and orgc_id from the field list. (5) Added the __mayUpdateCapturedCluster() private method implementing the three-way authorization check. In tests/testregressions.py: added a GalaxyClusterCaptureUpdateGate test class with six test cases covering cross-org refusal, owner acceptance, sync-user visibility gating, and ownership preservation.",
"patchTruncated": false,
"patches": [
{
"commit": "4ac836afde4a29a90cd19322f6fb75a6940fb731",
"date": "Tue, 10 Nov 2026 17:49:32 +0100",
"patchSha256": "7d89e603fc49aaccca3169da87afdcc8fe49cdf1a05aa2aa6108ffe188f61c39",
"retrievedAt": "2026-11-18T21:09:33.577220Z",
"source": "https://github.com/MISP/MISP/commit/4ac836afd.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/4ac836afd.patch",
"subject": "fix: [security] Galaxy cluster imports no longer take over"
}
],
"source": "https://github.com/MISP/MISP/commit/4ac836afd.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T21:10:16Z",
"version": "2.0.3"
},
"subject": "fix: [security] Galaxy cluster imports no longer take over",
"weaknessRationale": [
{
"cweId": "CWE-862",
"rationale": "The captureCluster() update path performed no check that the requesting user was authorized to modify the specific cluster identified by UUID. Any user with the galaxy editor role could update and take ownership of clusters belonging to other organizations. The authorization logic was entirely absent for the cross-organization case."
},
{
"cweId": "CWE-639",
"rationale": "The cluster UUID, supplied by the attacker in the import payload, was used as the sole key to identify the target row for update without verifying that the caller had a legitimate relationship (ownership, sharing-group visibility, or admin role) to that specific resource."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (4ac836afde4a29a90cd19322f6fb75a6940fb731): fix: [security] Galaxy cluster imports no longer take over",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/4ac836afd.patch"
],
"timestamp": "2026-11-10T16:49:32Z",
"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/4ac836afd.patch"
],
"timestamp": "2026-11-18T21:09:33.577220Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20201"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-132644",
"datePublished": "2026-11-18T21:13:49.544Z",
"dateReserved": "2026-11-18T21:13:46.525Z",
"dateUpdated": "2026-11-18T21:24:21.209Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-132247 (GCVE-0-2026-132247)
Vulnerability from cvelistv5 – Published: 2026-11-18 17:07 – Updated: 2026-11-18 18:14{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-132247",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T17:37:21.826938Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T18:14:58.037Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "TeamCity",
"vendor": "JetBrains",
"versions": [
{
"lessThan": "2026.1.3",
"status": "affected",
"version": "2026.1",
"versionType": "semver"
},
{
"lessThan": "2025.11.7",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eIn JetBrains TeamCity before 2026.1.3, 2025.11.7 improper authorization allowed viewing build process details via agent stacktraces\u003c/p\u003e"
}
],
"value": "In JetBrains TeamCity before 2026.1.3, 2025.11.7 improper authorization allowed viewing build process details via agent stacktraces"
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-639",
"description": "CWE-639",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T17:55:14.561Z",
"orgId": "547ada31-17d8-4964-bc5f-1b8238ba8014",
"shortName": "JetBrains"
},
"references": [
{
"url": "https://www.jetbrains.com/privacy-security/issues-fixed/"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "547ada31-17d8-4964-bc5f-1b8238ba8014",
"assignerShortName": "JetBrains",
"cveId": "CVE-2026-132247",
"datePublished": "2026-11-18T17:07:59.174Z",
"dateReserved": "2026-11-18T16:31:17.014Z",
"dateUpdated": "2026-11-18T18:14:58.037Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-132245 (GCVE-0-2026-132245)
Vulnerability from cvelistv5 – Published: 2026-11-18 17:07 – Updated: 2026-11-18 18:15{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-132245",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T17:38:07.032784Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T18:15:28.392Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "TeamCity",
"vendor": "JetBrains",
"versions": [
{
"lessThan": "2026.1.3",
"status": "affected",
"version": "2026.1",
"versionType": "semver"
},
{
"lessThan": "2025.11.7",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eIn JetBrains TeamCity before 2026.1.3, 2025.11.7 DoS via agent command results was possible\u003c/p\u003e"
}
],
"value": "In JetBrains TeamCity before 2026.1.3, 2025.11.7 DoS via agent command results was possible"
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-639",
"description": "CWE-639",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T17:54:55.729Z",
"orgId": "547ada31-17d8-4964-bc5f-1b8238ba8014",
"shortName": "JetBrains"
},
"references": [
{
"url": "https://www.jetbrains.com/privacy-security/issues-fixed/"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "547ada31-17d8-4964-bc5f-1b8238ba8014",
"assignerShortName": "JetBrains",
"cveId": "CVE-2026-132245",
"datePublished": "2026-11-18T17:07:58.196Z",
"dateReserved": "2026-11-18T16:31:16.453Z",
"dateUpdated": "2026-11-18T18:15:28.392Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-132144 (GCVE-0-2026-132144)
Vulnerability from cvelistv5 – Published: 2026-11-18 20:41 – Updated: 2026-11-18 20:54| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/a1fe5058dc758… | patch |
qwen3.8:27b
2 events
advisory
bcp-05-x-01bcp-05-x-02bcp-05-x-03
Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.
| Model | Source | Identifier |
|---|---|---|
| qwen3.8:27b | ollama | qwen3.8:27b |
- Generator
-
patch2vuln.pyon 2026-11-18 13:14 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/a1fe5058dc758b0e91bb0ff72f622fa99bdfd873.patch
502df2ebb69b… - Confidence
- high
| Commit | Subject | Patch SHA-256 |
|---|---|---|
a1fe5058dc75
|
fix: [security] Login e-mails are admin-only under external | 502df2ebb69b… |
Fix summary
The authorization check for changing a login email now explicitly denies the operation for non-site-admin users when any external authentication backend is active (Security.auth is set, ApacheSecureAuth.apacheEnv is configured, or Plugin.CustomAuth_enable is true). Only site administrators retain the ability to modify login emails in an external-authentication deployment, preventing non-admin users from redirecting their directory identity lookup to an arbitrary account.
Patch summary
In app/Controller/UsersController.php, the __canChangeLogin() method was restructured: after the existing site-admin bypass and MISP.disable_user_login_change check, three additional conditions are now required for non-admins to change their login email: Security.auth must be empty, ApacheSecureAuth.apacheEnv must be unset, and Plugin.CustomAuth_enable must be unset. A new regression test class LoginChangeExternalAuth in tests/testregressions.py verifies that self-service and org-admin email changes are refused when external auth is enabled, while site-admin changes remain permitted, and that self-service changes still work when no external auth is configured.
CVSS rationale
AV:N: MISP is a network-accessible web application. AC:L: The attack is a single API call to change the email field; no race conditions or special timing are needed. AT:N: No prior tampering of system data is required. PR:L: An authenticated non-admin user with a valid API key is sufficient. UI:N: No victim interaction is needed; the attacker acts on their own account. VC:L: The attacker gains read access to data visible to the captured identity. VI:H: The integrity of the identity-to-account binding is fundamentally broken; the attacker assumes a different identity and its privileges. VA:N: No denial-of-service impact. SC:N: No secondary-component confidentiality impact beyond what is captured. SI:H: The external directory's identity resolution is subverted for the attacker's session. SA:N: No availability impact on the directory service.
Weakness rationale
- CWE-285 The __canChangeLogin() authorization check failed to restrict the login-email change action based on the active authentication context. When external authentication was in use, the check should have denied non-admin email changes because the email is the directory identity key, but it only evaluated a single configuration flag.
- CWE-639 The login email is a user-controlled key used by the external directory to resolve identity. Because non-admins could modify this key, they could redirect the directory lookup to an arbitrary account, bypassing the intended identity binding.
Attack pattern rationale
- CAPEC-126 The attacker, holding a low-privilege MISP account, changes their login email to match a higher-privilege directory account. On next login the external backend resolves the email to the target identity, granting the attacker the target's organization and role. This is a direct privilege escalation via identity capture. The mapping is the closest standard CAPEC; no more specific CAPEC for directory-identity capture exists in the CAPEC catalog.
Assumptions to verify
- The affected MISP version range is not specified in the patch; all versions prior to this commit that lack the external-auth check in __canChangeLogin() are assumed affected.
- The vulnerability requires that at least one external authentication backend (Security.auth, ApacheSecureAuth, or CustomAuth) is configured; instances using only local MISP authentication are not affected by this specific issue.
- The CVSS VC:L assumes the attacker gains data access scoped to the captured identity's permissions; a higher-privilege target could yield higher confidentiality impact.
- CAPEC-126 (Privilege Escalation) is the closest standard mapping; no CAPEC specifically covers directory-identity capture via email-key substitution.
- The SSVC technical_impact of 'total' assumes the captured directory identity's full privilege set is transferred to the attacker; if the target identity has limited privileges, the practical impact may be lower.
- The commit date (2026-11-18) and AI co-authorship (Claude Opus 5.5) are noted from metadata but do not affect the vulnerability analysis.
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 |
7 | 11 | high | 6 |
- 2026-11-18 09:15 UTC Fix developed Corrective change authored (a1fe5058dc758b0e91bb0ff72f622fa99bdfd873): fix: [security] Login e-mails are admin-only under external https://github.com/MISP/MISP/commit/a1fe5058dc758b0e91bb0ff72f622fa99bdfd873.patch
- 2026-11-18 13:14 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/a1fe5058dc758b0e91bb0ff72f622fa99bdfd873.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-132144",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T20:53:57.986486Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T20:54:07.518Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"UsersController (app/Controller/UsersController.php)"
],
"product": "misp",
"programFiles": [
"app/Controller/UsersController.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:*:*:*:*:*:*:*:*",
"versionEndIncluding": "2.5.51",
"versionStartIncluding": "0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Francois-Xavier Stellamans from the NATO Cyber Security Centre with OpenAI Daybreak support (using GPT5.6-Cyber)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
}
],
"descriptions": [
{
"lang": "en",
"value": "MISP contains an authorization flaw in the user login-email change logic. When an external authentication backend is configured (LDAP, Shibboleth, ApacheSecureAuth, or CustomAuth), the login email address serves as the key by which the directory service resolves a user\u0027s identity, organization, and role on each login. The __canChangeLogin() method in UsersController only checked the MISP.disable_user_login_change setting and site-admin status; it did not account for whether an external authentication backend was active. As a result, any authenticated non-admin user (including org admins) could change their own login email to an address that matches a higher-privilege account in the external directory. On the user\u0027s next login, the external backend would resolve that email to the target directory identity, granting the attacker the organization and role associated with that identity. This constitutes an account-identity capture and privilege escalation: the attacker effectively assumes the identity of any directory account whose email they can guess or discover. The vulnerability requires an authenticated session with a valid API key or session token and a MISP instance configured with at least one external authentication backend. The impact is limited to the scope of the captured directory identity\u0027s privileges within MISP."
}
],
"impacts": [
{
"capecId": "CAPEC-126",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-126 Privilege Escalation"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.3,
"baseSeverity": "HIGH",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "HIGH",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:H/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T13:14:53Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-285",
"description": "CWE-285 Improper Authorization",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-639",
"description": "CWE-639 Authorization Bypass Through User-Controlled Key",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T20:41:10.546Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/a1fe5058dc758b0e91bb0ff72f622fa99bdfd873"
}
],
"solutions": [
{
"lang": "en",
"value": "The authorization check for changing a login email now explicitly denies the operation for non-site-admin users when any external authentication backend is active (Security.auth is set, ApacheSecureAuth.apacheEnv is configured, or Plugin.CustomAuth_enable is true). Only site administrators retain the ability to modify login emails in an external-authentication deployment, preventing non-admin users from redirecting their directory identity lookup to an arbitrary account."
}
],
"title": "MISP: Non-admin users can change login email under external authentication to capture a directory identity",
"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 affected MISP version range is not specified in the patch; all versions prior to this commit that lack the external-auth check in __canChangeLogin() are assumed affected.",
"The vulnerability requires that at least one external authentication backend (Security.auth, ApacheSecureAuth, or CustomAuth) is configured; instances using only local MISP authentication are not affected by this specific issue.",
"The CVSS VC:L assumes the attacker gains data access scoped to the captured identity\u0027s permissions; a higher-privilege target could yield higher confidentiality impact.",
"CAPEC-126 (Privilege Escalation) is the closest standard mapping; no CAPEC specifically covers directory-identity capture via email-key substitution.",
"The SSVC technical_impact of \u0027total\u0027 assumes the captured directory identity\u0027s full privilege set is transferred to the attacker; if the target identity has limited privileges, the practical impact may be lower.",
"The commit date (2026-11-18) and AI co-authorship (Claude Opus 5.5) are noted from metadata but do not affect the vulnerability analysis."
],
"capecRationale": [
{
"capecId": "CAPEC-126",
"rationale": "The attacker, holding a low-privilege MISP account, changes their login email to match a higher-privilege directory account. On next login the external backend resolves the email to the target identity, granting the attacker the target\u0027s organization and role. This is a direct privilege escalation via identity capture. The mapping is the closest standard CAPEC; no more specific CAPEC for directory-identity capture exists in the CAPEC catalog."
}
],
"commit": "a1fe5058dc758b0e91bb0ff72f622fa99bdfd873",
"confidence": "high",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Francois-Xavier Stellamans from the NATO Cyber Security Centre with OpenAI Daybreak support (using GPT5.6-Cyber)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
}
],
"cvssRationale": "AV:N: MISP is a network-accessible web application. AC:L: The attack is a single API call to change the email field; no race conditions or special timing are needed. AT:N: No prior tampering of system data is required. PR:L: An authenticated non-admin user with a valid API key is sufficient. UI:N: No victim interaction is needed; the attacker acts on their own account. VC:L: The attacker gains read access to data visible to the captured identity. VI:H: The integrity of the identity-to-account binding is fundamentally broken; the attacker assumes a different identity and its privileges. VA:N: No denial-of-service impact. SC:N: No secondary-component confidentiality impact beyond what is captured. SI:H: The external directory\u0027s identity resolution is subverted for the attacker\u0027s session. SA:N: No availability impact on the directory service.",
"draft": false,
"fixSummary": "The authorization check for changing a login email now explicitly denies the operation for non-site-admin users when any external authentication backend is active (Security.auth is set, ApacheSecureAuth.apacheEnv is configured, or Plugin.CustomAuth_enable is true). Only site administrators retain the ability to modify login emails in an external-authentication deployment, preventing non-admin users from redirecting their directory identity lookup to an arbitrary account.",
"generatedAt": "2026-11-18T13:14:53.442286Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 6,
"confidence": "high",
"model": "qwen3.8:27b",
"score": 7
}
],
"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": "502df2ebb69b222bcd0fa06bfab41c03d904d3c8b67ca24ef25f98e8042dc60d",
"patchSummary": "In app/Controller/UsersController.php, the __canChangeLogin() method was restructured: after the existing site-admin bypass and MISP.disable_user_login_change check, three additional conditions are now required for non-admins to change their login email: Security.auth must be empty, ApacheSecureAuth.apacheEnv must be unset, and Plugin.CustomAuth_enable must be unset. A new regression test class LoginChangeExternalAuth in tests/testregressions.py verifies that self-service and org-admin email changes are refused when external auth is enabled, while site-admin changes remain permitted, and that self-service changes still work when no external auth is configured.",
"patchTruncated": false,
"patches": [
{
"commit": "a1fe5058dc758b0e91bb0ff72f622fa99bdfd873",
"date": "Wed, 18 Nov 2026 10:15:00 +0100",
"patchSha256": "502df2ebb69b222bcd0fa06bfab41c03d904d3c8b67ca24ef25f98e8042dc60d",
"retrievedAt": "2026-11-18T13:14:06.772159Z",
"source": "https://github.com/MISP/MISP/commit/a1fe5058dc758b0e91bb0ff72f622fa99bdfd873.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/a1fe5058dc758b0e91bb0ff72f622fa99bdfd873.patch",
"subject": "fix: [security] Login e-mails are admin-only under external"
}
],
"source": "https://github.com/MISP/MISP/commit/a1fe5058dc758b0e91bb0ff72f622fa99bdfd873.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T13:14:53Z",
"version": "2.0.3"
},
"subject": "fix: [security] Login e-mails are admin-only under external",
"weaknessRationale": [
{
"cweId": "CWE-285",
"rationale": "The __canChangeLogin() authorization check failed to restrict the login-email change action based on the active authentication context. When external authentication was in use, the check should have denied non-admin email changes because the email is the directory identity key, but it only evaluated a single configuration flag."
},
{
"cweId": "CWE-639",
"rationale": "The login email is a user-controlled key used by the external directory to resolve identity. Because non-admins could modify this key, they could redirect the directory lookup to an arbitrary account, bypassing the intended identity binding."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (a1fe5058dc758b0e91bb0ff72f622fa99bdfd873): fix: [security] Login e-mails are admin-only under external",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/a1fe5058dc758b0e91bb0ff72f622fa99bdfd873.patch"
],
"timestamp": "2026-11-18T09:15:00Z",
"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/a1fe5058dc758b0e91bb0ff72f622fa99bdfd873.patch"
],
"timestamp": "2026-11-18T13:14:06.772159Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20351"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-132144",
"datePublished": "2026-11-18T20:41:10.546Z",
"dateReserved": "2026-11-18T13:21:34.157Z",
"dateUpdated": "2026-11-18T20:54:07.518Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-132137 (GCVE-0-2026-132137)
Vulnerability from cvelistv5 – Published: 2026-11-18 20:15 – Updated: 2026-11-18 20:15| URL | Tags |
|---|---|
| https://vuldb.com/vuln/439437 | vdb-entrytechnical-description |
| https://vuldb.com/vuln/439437/cti | signaturepermissions-required |
| https://vuldb.com/cve/CVE-2026-132137 | third-party-advisory |
| https://vuldb.com/submit/958679 | third-party-advisory |
| https://github.com/Bob-wentao/relaticle-import-wi… | exploit |
{
"containers": {
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:relaticle:relaticle:*:*:*:*:*:*:*:*"
],
"modules": [
"Import Wizard"
],
"product": "Relaticle",
"vendor": "n/a",
"versions": [
{
"status": "affected",
"version": "3.0"
},
{
"status": "affected",
"version": "3.1"
},
{
"status": "affected",
"version": "3.2"
},
{
"status": "affected",
"version": "3.3"
},
{
"status": "affected",
"version": "3.4"
},
{
"status": "affected",
"version": "3.5"
},
{
"status": "affected",
"version": "3.6"
},
{
"status": "affected",
"version": "3.7"
},
{
"status": "affected",
"version": "3.8"
},
{
"status": "affected",
"version": "3.9"
},
{
"status": "affected",
"version": "3.10.0"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "bobtao666 (VulDB User)"
},
{
"lang": "en",
"type": "coordinator",
"value": "VulDB CNA Team"
}
],
"descriptions": [
{
"lang": "en",
"value": "A vulnerability was identified in Relaticle up to 3.10.0. This affects the function mapToField of the file packages/ImportWizard/src/Livewire/Steps/MappingStep.php of the component Import Wizard. Such manipulation of the argument Target leads to authorization bypass. The attack can be executed remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure."
}
],
"metrics": [
{
"cvssV4_0": {
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P",
"version": "4.0"
}
},
{
"cvssV3_1": {
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C",
"version": "3.1"
}
},
{
"cvssV3_0": {
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C",
"version": "3.0"
}
},
{
"cvssV2_0": {
"baseScore": 6.5,
"vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:C",
"version": "2.0"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-639",
"description": "Authorization Bypass",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-285",
"description": "Improper Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T20:15:16.615Z",
"orgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
"shortName": "VulDB"
},
"references": [
{
"name": "VDB-439437 | Relaticle Import Wizard MappingStep.php mapToField authorization",
"tags": [
"vdb-entry",
"technical-description"
],
"url": "https://vuldb.com/vuln/439437"
},
{
"name": "VDB-439437 | CTI Indicators (IOB, IOC, IOA)",
"tags": [
"signature",
"permissions-required"
],
"url": "https://vuldb.com/vuln/439437/cti"
},
{
"name": "CVE-2026-132137 | CVE Analysis and Report",
"tags": [
"third-party-advisory"
],
"url": "https://vuldb.com/cve/CVE-2026-132137"
},
{
"name": "Submit #958679 | Relaticle \u003c=3.5.6 IDOR",
"tags": [
"third-party-advisory"
],
"url": "https://vuldb.com/submit/958679"
},
{
"tags": [
"exploit"
],
"url": "https://github.com/Bob-wentao/relaticle-import-wizard-security-research"
}
],
"timeline": [
{
"lang": "en",
"time": "2026-11-18T00:00:00.000Z",
"value": "Advisory disclosed"
},
{
"lang": "en",
"time": "2026-11-18T01:00:00.000Z",
"value": "VulDB entry created"
},
{
"lang": "en",
"time": "2026-11-18T14:09:07.000Z",
"value": "VulDB entry last update"
}
],
"title": "Relaticle Import Wizard MappingStep.php mapToField authorization",
"x_generator": [
"VulDB PVTS v202611"
]
}
},
"cveMetadata": {
"assignerOrgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
"assignerShortName": "VulDB",
"cveId": "CVE-2026-132137",
"datePublished": "2026-11-18T20:15:16.615Z",
"dateReserved": "2026-11-18T13:03:28.960Z",
"dateUpdated": "2026-11-18T20:15:16.615Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-130872 (GCVE-0-2026-130872)
Vulnerability from cvelistv5 – Published: 2026-11-17 19:47 – Updated: 2026-11-18 16:17- CWE-639 - Authorization Bypass Through User-Controlled Key
| URL | Tags |
|---|---|
| https://github.com/pytition/Pytition/issues/347 | issue-tracking |
| https://github.com/pytition/Pytition/commit/d6301… | patch |
| https://github.com/pytition/Pytition/releases/tag/v2.10 | release-notes |
| https://github.com/pytition/Pytition/blob/v2.9/py… | technical-description |
| https://www.vulncheck.com/advisories/pytition-bef… | third-party-advisory |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-130872",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T16:16:07.576964Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T16:17:21.373Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:github/pytition/pytition",
"product": "Pytition",
"repo": "https://github.com/pytition/Pytition",
"vendor": "Pytition",
"versions": [
{
"lessThan": "2.10",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "George Chen"
}
],
"datePublic": "2026-11-17T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Pytition before 2.10 contains an insecure direct object reference vulnerability in the show_signatures view that allows registered users to delete other petitions\u0027 signatures by supplying foreign signature IDs. Attackers can post sequential signature IDs to their own petition\u0027s signatures page to permanently delete signatures from any user-owned petition and trigger confirmation emails to other signers."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"privilegesRequired": "LOW",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "HIGH"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-639",
"description": "Authorization Bypass Through User-Controlled Key",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T19:47:26.064Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"tags": [
"issue-tracking"
],
"url": "https://github.com/pytition/Pytition/issues/347"
},
{
"tags": [
"patch"
],
"url": "https://github.com/pytition/Pytition/commit/d6301dd6e3774b292fdc04a072b9c9914b9237c3"
},
{
"name": "Pytition v2.10 Release Notes",
"tags": [
"release-notes"
],
"url": "https://github.com/pytition/Pytition/releases/tag/v2.10"
},
{
"tags": [
"technical-description"
],
"url": "https://github.com/pytition/Pytition/blob/v2.9/pytition/petition/views.py#L1424-L1440"
},
{
"name": "VulnCheck Advisory: Pytition before 2.10 IDOR Signature Deletion via show_signatures View",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/pytition-before-2.10-idor-signature-deletion-via-show-signatures-view"
}
],
"title": "Pytition before 2.10 IDOR Signature Deletion via show_signatures View",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-130872",
"datePublished": "2026-11-17T19:47:26.064Z",
"dateReserved": "2026-11-17T17:51:34.220Z",
"dateUpdated": "2026-11-18T16:17:21.373Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Mitigation
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Mitigation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Mitigation
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
No CAPEC attack patterns related to this CWE.