Find a vulnerability
Search criteria
1371 vulnerabilities
CVE-2026-128978 (GCVE-0-2026-128978)
Vulnerability from cvelistv5 – Published: 2026-11-19 17:41 – Updated: 2026-11-19 19:50- CWE-295 - Improper certificate validation
| URL | Tags |
|---|---|
| https://github.com/open-eid/libdigidocpp/security… | release-notes |
| https://www.id.ee/artikkel/uus-id-tarkvara-versio… | government-resource |
| Vendor | Product | Version | |
|---|---|---|---|
| Estonian Information System Authority (RIA) | libdigidocpp |
Affected:
3.13.0 , < 4.5.2
(semver)
|
|
| Estonian Information System Authority (RIA) | DigiDoc4 |
Affected:
4.0.0 , < 4.11.2
(semver)
|
|
| Estonian Information System Authority (RIA) | DigiDoc |
Affected:
3.0.0 , < 3.2.0
(semver)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-128978",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T17:49:41.960542Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T19:50:39.234Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "libdigidocpp",
"vendor": "Estonian Information System Authority (RIA)",
"versions": [
{
"lessThan": "4.5.2",
"status": "affected",
"version": "3.13.0",
"versionType": "semver"
}
]
},
{
"defaultStatus": "unaffected",
"product": "DigiDoc4",
"vendor": "Estonian Information System Authority (RIA)",
"versions": [
{
"lessThan": "4.11.2",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
}
]
},
{
"defaultStatus": "unaffected",
"platforms": [
"Android",
"iOS"
],
"product": "DigiDoc",
"vendor": "Estonian Information System Authority (RIA)",
"versions": [
{
"lessThan": "3.2.0",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Improper certificate validation vulnerability in Estonian Information System Authority (RIA) libdigidocpp, Estonian Information System Authority (RIA) DigiDoc4, and Estonian Information System Authority (RIA) DigiDoc on Android and iOS.\u003cp\u003eThis issue affects libdigidocpp: from 3.13.0 before 4.5.2; DigiDoc4: from 4.0.0 before 4.11.2; DigiDoc: from 3.0.0 before 3.2.0.\u003c/p\u003e"
}
],
"value": "Improper certificate validation vulnerability in Estonian Information System Authority (RIA) libdigidocpp, Estonian Information System Authority (RIA) DigiDoc4, and Estonian Information System Authority (RIA) DigiDoc on Android and iOS.\n\nThis issue affects libdigidocpp: from 3.13.0 before 4.5.2; DigiDoc4: from 4.0.0 before 4.11.2; DigiDoc: from 3.0.0 before 3.2.0."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 6,
"baseSeverity": "MEDIUM",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-295",
"description": "CWE-295 Improper certificate validation",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T17:41:24.836Z",
"orgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"shortName": "ENISA"
},
"references": [
{
"tags": [
"release-notes"
],
"url": "https://github.com/open-eid/libdigidocpp/security/advisories/GHSA-q2rc-qw4c-8gv5"
},
{
"tags": [
"government-resource"
],
"url": "https://www.id.ee/artikkel/uus-id-tarkvara-versioon-parandab-kaks-olulist-turvanrkust/"
}
],
"title": "Improper Verification of Cryptographic Signatures in libdigidocpp",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"assignerShortName": "ENISA",
"cveId": "CVE-2026-128978",
"datePublished": "2026-11-19T17:41:24.836Z",
"dateReserved": "2026-11-13T13:48:09.132Z",
"dateUpdated": "2026-11-19T19:50:39.234Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-22308 (GCVE-0-2026-22308)
Vulnerability from cvelistv5 – Published: 2026-11-19 17:17 – Updated: 2026-11-19 20:53| URL | Tags |
|---|---|
| https://www.jtl-software.com/de/security/sicherhe… | vendor-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| JTL-Software GmbH | JTL-Shop |
Affected:
5.8.0 , < 5.8.4
(semver)
Affected: 5.7.0 , < 5.7.6 (semver) Affected: 5.6.0 , < 5.6.6 (semver) Affected: 5.5.0 , < 5.5.4 (semver) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-22308",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T20:53:18.642765Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T20:53:38.159Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "JTL-Shop",
"vendor": "JTL-Software GmbH",
"versions": [
{
"lessThan": "5.8.4",
"status": "affected",
"version": "5.8.0",
"versionType": "semver"
},
{
"lessThan": "5.7.6",
"status": "affected",
"version": "5.7.0",
"versionType": "semver"
},
{
"lessThan": "5.6.6",
"status": "affected",
"version": "5.6.0",
"versionType": "semver"
},
{
"lessThan": "5.5.4",
"status": "affected",
"version": "5.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Lionel Machire (Metzler GmbH) and Lucas Nill"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003e\n\n\n\u003c/p\u003e\u003cp\u003e\n\n\n\u003c/p\u003e\u003cp\u003eThe preview mode of the OPC (OnPage Composer) page\nbuilder of JTL-Shop is activated by a request parameter alone and\nrenders page data supplied in the request without checking for an authenticated\nbackend session with the corresponding permission. Several portlet properties\nare output without output encoding. An unauthenticated remote attacker\ncan thereby cause script code to be executed in the browser of a\nvisitor or administrator who opens a crafted link; in the case of an\nadministrator, actions can be performed with the administrator\u0027s privileges. Third-party\nplugins whose portlets evaluate property values as templates can\nadditionally be made to execute template code through the same entry point. This is\na separate flaw in such plugins and does not affect the portlets of JTL-Shop itself.\u003c/p\u003e"
}
],
"value": "The preview mode of the OPC (OnPage Composer) page\nbuilder of JTL-Shop is activated by a request parameter alone and\nrenders page data supplied in the request without checking for an authenticated\nbackend session with the corresponding permission. Several portlet properties\nare output without output encoding. An unauthenticated remote attacker\ncan thereby cause script code to be executed in the browser of a\nvisitor or administrator who opens a crafted link; in the case of an\nadministrator, actions can be performed with the administrator\u0027s privileges. Third-party\nplugins whose portlets evaluate property values as templates can\nadditionally be made to execute template code through the same entry point. This is\na separate flaw in such plugins and does not affect the portlets of JTL-Shop itself."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 9.3,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.6,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-306",
"description": "CWE-306 Missing authentication for critical function",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-79",
"description": "CWE-79 Improper neutralization of input during web page generation (\u0027cross-site scripting\u0027)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T17:17:06.172Z",
"orgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"shortName": "ENISA"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://www.jtl-software.com/de/security/sicherheitshinweis-opc-vorschaumodus_xss/"
}
],
"title": "Missing authentication for critical function leading to reflected cross-site scripting in JTL-Shop",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"assignerShortName": "ENISA",
"cveId": "CVE-2026-22308",
"datePublished": "2026-11-19T17:17:06.172Z",
"dateReserved": "2026-01-07T09:31:00.563Z",
"dateUpdated": "2026-11-19T20:53:38.159Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-22309 (GCVE-0-2026-22309)
Vulnerability from cvelistv5 – Published: 2026-11-19 17:11 – Updated: 2026-11-19 20:50- CWE-79 - Improper neutralization of input during web page generation ('cross-site scripting')
| URL | Tags |
|---|---|
| https://www.jtl-software.com/de/security/sicherhe… | vendor-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| JTL-Software GmbH | JTL-Shop |
Affected:
5.8.0 , < 5.8.4
(semver)
Affected: 5.7.0 , < 5.7.6 (semver) Affected: 5.6.0 , < 5.6.6 (semver) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-22309",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T20:50:13.073805Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T20:50:22.456Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "JTL-Shop",
"vendor": "JTL-Software GmbH",
"versions": [
{
"lessThan": "5.8.4",
"status": "affected",
"version": "5.8.0",
"versionType": "semver"
},
{
"lessThan": "5.7.6",
"status": "affected",
"version": "5.7.0",
"versionType": "semver"
},
{
"lessThan": "5.6.6",
"status": "affected",
"version": "5.6.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Elka\u00f1o"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003e\n\n\n\u003c/p\u003e\u003cp\u003eThe visitor tracking of JTL-Shop automatically\nregisters unknown crawler user agents without filtering the value, and the stored\nvalue is rendered without output encoding on several pages of the\nadministration backend (search engine statistics, crawler dashboard widget, crawler\nedit form, sitemap export download list and campaign details). An\nunauthenticated remote attacker can store script code with a single request. The code is\nexecuted in the browser session of an administrator who opens one of these\npages, allowing actions to be performed with the administrator\u0027s privileges.\u003c/p\u003e"
}
],
"value": "The visitor tracking of JTL-Shop automatically\nregisters unknown crawler user agents without filtering the value, and the stored\nvalue is rendered without output encoding on several pages of the\nadministration backend (search engine statistics, crawler dashboard widget, crawler\nedit form, sitemap export download list and campaign details). An\nunauthenticated remote attacker can store script code with a single request. The code is\nexecuted in the browser session of an administrator who opens one of these\npages, allowing actions to be performed with the administrator\u0027s privileges."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 9.3,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.6,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-79",
"description": "CWE-79 Improper neutralization of input during web page generation (\u0027cross-site scripting\u0027)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T17:11:57.925Z",
"orgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"shortName": "ENISA"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://www.jtl-software.com/de/security/sicherheitshinweis-crawler-user-agent_xss/"
}
],
"title": "Stored cross-site scripting in JTL-Shop",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"assignerShortName": "ENISA",
"cveId": "CVE-2026-22309",
"datePublished": "2026-11-19T17:11:57.925Z",
"dateReserved": "2026-01-07T09:31:00.563Z",
"dateUpdated": "2026-11-19T20:50:22.456Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-22310 (GCVE-0-2026-22310)
Vulnerability from cvelistv5 – Published: 2026-11-19 16:57 – Updated: 2026-11-19 20:48- CWE-79 - Improper neutralization of input during web page generation ('cross-site scripting')
| URL | Tags |
|---|---|
| https://www.jtl-software.com/de/security/sicherhe… | vendor-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| JTL-Software GmbH | JTL-Shop |
Affected:
5.8.0 , < 5.8.4
(semver)
Affected: 5.7.0 , < 5.7.6 (semver) Affected: 5.6.0 , < 5.6.6 (semver) Affected: 5.5.0 , < 5.5.5 (semver) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-22310",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T20:48:14.504534Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T20:48:24.617Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "JTL-Shop",
"vendor": "JTL-Software GmbH",
"versions": [
{
"lessThan": "5.8.4",
"status": "affected",
"version": "5.8.0",
"versionType": "semver"
},
{
"lessThan": "5.7.6",
"status": "affected",
"version": "5.7.0",
"versionType": "semver"
},
{
"lessThan": "5.6.6",
"status": "affected",
"version": "5.6.0",
"versionType": "semver"
},
{
"lessThan": "5.5.5",
"status": "affected",
"version": "5.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Elka\u00f1o"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eWhen the setting for saving requests to non-existent\npages (404) is enabled, JTL-Shop stores the raw requested URL in its\nredirect table, and the administration backend renders it without output\nencoding in the form used to edit a redirect. An unauthenticated remote\nattacker can store script code with a single request, which is executed in the\nbrowser session of an administrator who opens the affected redirect,\nallowing actions to be performed with the administrator\u0027s privileges. The\nsetting is disabled by default in new installations but may still be\nenabled in older ones.\u003c/p\u003e"
}
],
"value": "When the setting for saving requests to non-existent\npages (404) is enabled, JTL-Shop stores the raw requested URL in its\nredirect table, and the administration backend renders it without output\nencoding in the form used to edit a redirect. An unauthenticated remote\nattacker can store script code with a single request, which is executed in the\nbrowser session of an administrator who opens the affected redirect,\nallowing actions to be performed with the administrator\u0027s privileges. The\nsetting is disabled by default in new installations but may still be\nenabled in older ones."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 7.6,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-79",
"description": "CWE-79 Improper neutralization of input during web page generation (\u0027cross-site scripting\u0027)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T16:57:14.565Z",
"orgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"shortName": "ENISA"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://www.jtl-software.com/de/security/sicherheitshinweis-404-weiterleitungen_xss/"
}
],
"title": "Stored cross-site scripting in JTL-Shop",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"assignerShortName": "ENISA",
"cveId": "CVE-2026-22310",
"datePublished": "2026-11-19T16:57:14.565Z",
"dateReserved": "2026-01-07T09:31:00.563Z",
"dateUpdated": "2026-11-19T20:48:24.617Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-87868 (GCVE-0-2026-87868)
Vulnerability from cvelistv5 – Published: 2026-11-19 15:04 – Updated: 2026-11-19 16:50 X_Open Source- CWE-328 - Use of weak hash
| URL | Tags |
|---|---|
| https://cert.pl/en/posts/2026/11/CVE-2026-87867 | third-party-advisory |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-87868",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T16:26:04.926928Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T16:50:30.561Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unknown",
"product": "MRemoteNG",
"repo": "https://github.com/mRemoteNG/mRemoteNG",
"vendor": "MRemoteNG",
"versions": [
{
"status": "affected",
"version": "1.76.20",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:mremoteng:mremoteng:1.76.20:*:*:*:*:*:*:*",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Maksymilian Kubiak"
},
{
"lang": "en",
"type": "finder",
"value": "Bart\u0142omiej Zalewski"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "MRemoteNG uses\u0026nbsp;single MD5 hash with no salt and no iterations for\u0026nbsp;key-derivation.\u0026nbsp;An attacker who obtains the encrypted data can brute-force\na weak or moderate passphrase offline at extreme speed and then decrypt every stored connection\npassword. When the default passphrase is in use, no cracking is needed at all; the key is derived from a\npublicly known value.\u003cdiv\u003e\u003cbr\u003e\u003c/div\u003e\u003cdiv\u003eVendor did not provide the range of vulnerable versions.\u0026nbsp;Only version\u0026nbsp;1.76.20 was tested and confirmed vulnerable.\u0026nbsp;Other versions may also be vulnerable.\u003c/div\u003e"
}
],
"value": "MRemoteNG uses\u00a0single MD5 hash with no salt and no iterations for\u00a0key-derivation.\u00a0An attacker who obtains the encrypted data can brute-force\na weak or moderate passphrase offline at extreme speed and then decrypt every stored connection\npassword. When the default passphrase is in use, no cracking is needed at all; the key is derived from a\npublicly known value.\n\n\nVendor did not provide the range of vulnerable versions.\u00a0Only version\u00a01.76.20 was tested and confirmed vulnerable.\u00a0Other versions may also be vulnerable."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "HIGH",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 8.2,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-328",
"description": "CWE-328 Use of weak hash",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T15:04:44.201Z",
"orgId": "4bb8329e-dd38-46c1-aafb-9bf32bcb93c6",
"shortName": "CERT-PL"
},
"references": [
{
"tags": [
"third-party-advisory"
],
"url": "https://cert.pl/en/posts/2026/11/CVE-2026-87867"
}
],
"source": {
"discovery": "EXTERNAL"
},
"tags": [
"x_open-source"
],
"title": "Use of weak hash in MRemoteNG",
"x_generator": {
"engine": "Vulnogram 1.0.3"
}
}
},
"cveMetadata": {
"assignerOrgId": "4bb8329e-dd38-46c1-aafb-9bf32bcb93c6",
"assignerShortName": "CERT-PL",
"cveId": "CVE-2026-87868",
"datePublished": "2026-11-19T15:04:44.201Z",
"dateReserved": "2026-09-09T13:22:16.913Z",
"dateUpdated": "2026-11-19T16:50:30.561Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-87867 (GCVE-0-2026-87867)
Vulnerability from cvelistv5 – Published: 2026-11-19 15:04 – Updated: 2026-11-19 16:50 X_Open Source- CWE-295 - Improper certificate validation
| URL | Tags |
|---|---|
| https://cert.pl/en/posts/2026/11/CVE-2026-87867 | third-party-advisory |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-87867",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T16:25:35.739468Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T16:50:45.904Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unknown",
"product": "MRemoteNG",
"repo": "https://github.com/mRemoteNG/mRemoteNG",
"vendor": "MRemoteNG",
"versions": [
{
"status": "affected",
"version": "1.76.20",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:mremoteng:mremoteng:1.76.20:*:*:*:*:*:*:*",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Maksymilian Kubiak"
},
{
"lang": "en",
"type": "finder",
"value": "Bart\u0142omiej Zalewski"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cdiv\u003eMRemoteNG establishes encrypted but unauthenticated channel\u0026nbsp;with\u0026nbsp;\u003cspan\u003eMicrosoft SQL Server backend. Client accepts any certificate the server\npresents, including a self-signed certificate supplied by an attacker. An attacker positioned between the client and the SQL server (for example via ARP/DNS spoofing) can\ntransparently p\u003c/span\u003eintercept the connection (man-in-the-middle) and read all traffic,\u003cspan\u003e\u0026nbsp;including the encrypted connection-password table read and the database login.\u003c/span\u003e\u003c/div\u003e\u003cdiv\u003e\u003cspan\u003e\u003cbr\u003e\u003c/span\u003e\u003c/div\u003e\u003cdiv\u003e\u003cspan\u003eVendor did not provide the range of vulnerable versions.\u0026nbsp;\u003c/span\u003e\u003cspan\u003eOnly version\u0026nbsp;\u003c/span\u003e\u003cspan\u003e1.76.20 was tested and confirmed vulnerable.\u0026nbsp;\u003c/span\u003e\u003cspan\u003eOther versions may also be vulnerable.\u003c/span\u003e\u003c/div\u003e"
}
],
"value": "MRemoteNG establishes encrypted but unauthenticated channel\u00a0with\u00a0Microsoft SQL Server backend. Client accepts any certificate the server\npresents, including a self-signed certificate supplied by an attacker. An attacker positioned between the client and the SQL server (for example via ARP/DNS spoofing) can\ntransparently pintercept the connection (man-in-the-middle) and read all traffic,\u00a0including the encrypted connection-password table read and the database login.\n\n\n\n\nVendor did not provide the range of vulnerable versions.\u00a0Only version\u00a01.76.20 was tested and confirmed vulnerable.\u00a0Other versions may also be vulnerable."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "ADJACENT",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-295",
"description": "CWE-295 Improper certificate validation",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T15:04:38.979Z",
"orgId": "4bb8329e-dd38-46c1-aafb-9bf32bcb93c6",
"shortName": "CERT-PL"
},
"references": [
{
"tags": [
"third-party-advisory"
],
"url": "https://cert.pl/en/posts/2026/11/CVE-2026-87867"
}
],
"source": {
"discovery": "EXTERNAL"
},
"tags": [
"x_open-source"
],
"title": "Improper Certificate Validation in MRemoteNG",
"x_generator": {
"engine": "Vulnogram 1.0.3"
}
}
},
"cveMetadata": {
"assignerOrgId": "4bb8329e-dd38-46c1-aafb-9bf32bcb93c6",
"assignerShortName": "CERT-PL",
"cveId": "CVE-2026-87867",
"datePublished": "2026-11-19T15:04:38.979Z",
"dateReserved": "2026-09-09T13:22:16.913Z",
"dateUpdated": "2026-11-19T16:50:45.904Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133190 (GCVE-0-2026-133190)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:44 – Updated: 2026-11-19 14:52| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/eee1f8b67 | 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-19 14:35 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/eee1f8b67.patch
ad525a5a8146… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
eee1f8b675c5
|
fix: [security] Revoked keys no longer sign protected events, | ad525a5a8146… |
Fix summary
The fix enforces key revocation in signature validation by skipping any key whose revoked flag is set before attempting PGP verification. It corrects the key-sync query to retrieve all stored keys (not just the first), ensures revocations are persisted and never lifted by a subsequent push, properly removes keys absent from the pushed list, and computes a fingerprint for entries that lack one so they match their stored counterpart. A signed protected event with no keys is now refused with a proper error response instead of an unhandled 500.
Patch summary
In CryptographicKey.php: (1) validateProtectedEvent() now checks $supplied_key['revoked'] and continues (skips) if set, before calling verifySignature(). (2) captureCryptographicKeyUpdate() changes find('first') to find('all') so all stored keys are considered. (3) A pre-loop computes a fingerprint via extractKeyData() for pushed entries that lack one. (4) The revocation branch is restructured: it now saves only the revoked flag (id + revoked=1) and the condition uses !empty() checks to ensure a revocation is never lifted. (5) The $existingKey array access is flattened (removing the nested 'CryptographicKey' key). (6) deleteAll() is guarded with an empty check on $toRemove. (7) The no-keys error message includes the event UUID and the log entry uses event ID 0. In tests/testregressions.py: a new ProtectedEventKeyRevocation test class adds nine regression tests covering revoked-key rejection, unrevoked-key acceptance, revocation persistence, non-lifting of revocations, key removal, fingerprint-less entry match
CVSS rationale
AV:N: MISP is a network-accessible web application; the attacker interacts via the HTTP API. AC:L: exploitation requires only signing an event with a revoked key and submitting it; no race conditions or special timing. AT:N: no special targeting beyond network reachability to the MISP instance. PR:L: the attacker must be an authenticated sync user with permission to add/edit protected events. UI:N: no victim interaction is required. VC:N: no confidentiality impact is evident. VI:H: integrity is significantly impacted because revoked keys retain signing authority and revocations are not applied, undermining the trust chain for protected events. VA:N: the 500-error issue is minor and does not constitute a meaningful availability impact. SC:N: no secondary confidentiality impact. SI:H: in a multi-instance MISP sync network, events signed by revoked keys can propagate to peer instances, extending the integrity compromise. SA:N: no secondary availability impact.
Weakness rationale
- CWE-345 The signature verification routine validated the cryptographic signature but failed to verify the authenticity/validity of the signing key by checking its revocation status. A revoked key was treated as a valid signing authority, which is a failure to fully verify data authenticity.
- CWE-287 The system accepted a revoked key as a valid credential for signing protected events, effectively failing to authenticate the signer's current authorization status. The key revocation mechanism was bypassed.
Attack pattern rationale
- CAPEC-124 The revoked-key state is an exceptional condition in the key lifecycle that the application failed to handle correctly during signature validation and key synchronization. The attacker exploits the system's failure to treat a revoked key as an exceptional (invalid) state. This is the closest CAPEC pattern; a more specific 'key revocation bypass' pattern does not exist in the CAPEC catalog, so CAPEC-124 is the best available match.
- CAPEC-100 The key-sync path is vulnerable to manipulation of the pushed key list: by omitting keys or crafting entries without fingerprints, an attacker can prevent revocations from being applied or cause valid keys to be removed. This is a secondary attack vector enabled by the same code defects. The mapping is approximate because the primary issue is a logic flaw rather than direct parameter injection.
Assumptions to verify
- The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.
- The attacker is assumed to be an authenticated sync user with permission to add or edit protected events; unauthenticated exploitation is not evidenced.
- The secondary integrity impact (SI:H) assumes a multi-instance MISP sync deployment; in a single-instance deployment the secondary impact may be lower.
- CAPEC-124 is selected as the closest available pattern; no CAPEC specifically covers cryptographic key revocation bypass, so the mapping is approximate.
- The Co-Authored-By line for Claude Opus 5.5 is treated as a tool credit; it is unclear whether this represents AI-assisted development or a placeholder.
- The 500-error issue (signed event without keys) is treated as a minor robustness defect subsumed under the primary revocation-bypass vulnerability rather than a separate issue.
- CVSS AT:N is used because the only options are N or P; the attacker does perform active interaction (submitting a signed event), but no special passive observation position is required.
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-14 11:53 UTC Fix developed Corrective change authored (eee1f8b675c5c472fa73b41982824c0c17dd639e): fix: [security] Revoked keys no longer sign protected events, https://github.com/MISP/MISP/commit/eee1f8b67.patch
- 2026-11-19 14:34 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/eee1f8b67.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133190",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:52:11.814868Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:52:25.872Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"CryptographicKey model (app/Model/CryptographicKey.php)"
],
"product": "misp",
"programFiles": [
"app/Model/CryptographicKey.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, a threat intelligence sharing platform, contains a vulnerability in its cryptographic key management for protected (PGP-signed) events. Two related defects allow a revoked PGP key to remain effective for signing and validating protected events.\n\nFirst, the validateProtectedEvent() method in the CryptographicKey model iterates over the event\u0027s stored cryptographic keys to verify a PGP signature but does not check the revoked flag on each key. A key explicitly marked as revoked is still used to validate signatures, meaning an entity whose key has been revoked can continue to sign protected events and have them accepted by the MISP instance.\n\nSecond, the captureCryptographicKeyUpdate() method, responsible for synchronizing the key list when a sync user edits a protected event, contained a query bug (find(\u0027first\u0027) instead of find(\u0027all\u0027)) that caused only the first stored key to be considered. As a result, revocations of additional keys were never persisted, keys absent from the pushed list were not removed, and entries lacking an explicit fingerprint were mismatched and incorrectly deleted. Additionally, the revocation logic did not enforce the invariant that a revocation, once stored, is never lifted by subsequent pushes.\n\nA third minor issue: a signed protected event submitted without any cryptographic keys triggered an unhandled 500 error rather than a proper rejection response.\n\nPreconditions: the attacker must be an authenticated sync user with permission to add or edit protected events on the MISP instance. The impact is that revoked keys retain signing authority, key revocations propagated by sync partners are silently dropped, and the integrity of the protected-event trust chain is compromised. In a multi-instance MISP deployment, events signed by revoked keys can propagate to other instances, extending the integrity impact across the sync network."
}
],
"impacts": [
{
"capecId": "CAPEC-124",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-124 Exploiting Incorrectly Handled Exceptional Conditions"
}
]
},
{
"capecId": "CAPEC-100",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-100 Parameter Tampering"
}
]
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 3.7,
"baseSeverity": "LOW",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:35:26Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"cvssV4_0": {
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-345",
"description": "CWE-345 Insufficient Verification of Data Authenticity",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-287",
"description": "CWE-287 Improper Authentication",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:44:46.132Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/eee1f8b67"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix enforces key revocation in signature validation by skipping any key whose revoked flag is set before attempting PGP verification. It corrects the key-sync query to retrieve all stored keys (not just the first), ensures revocations are persisted and never lifted by a subsequent push, properly removes keys absent from the pushed list, and computes a fingerprint for entries that lack one so they match their stored counterpart. A signed protected event with no keys is now refused with a proper error response instead of an unhandled 500."
}
],
"title": "MISP CryptographicKey: Revoked PGP Keys Still Validate Protected Event Signatures and Key Revocation Sync Is Ineffective",
"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 are assumed affected.",
"The attacker is assumed to be an authenticated sync user with permission to add or edit protected events; unauthenticated exploitation is not evidenced.",
"The secondary integrity impact (SI:H) assumes a multi-instance MISP sync deployment; in a single-instance deployment the secondary impact may be lower.",
"CAPEC-124 is selected as the closest available pattern; no CAPEC specifically covers cryptographic key revocation bypass, so the mapping is approximate.",
"The Co-Authored-By line for Claude Opus 5.5 is treated as a tool credit; it is unclear whether this represents AI-assisted development or a placeholder.",
"The 500-error issue (signed event without keys) is treated as a minor robustness defect subsumed under the primary revocation-bypass vulnerability rather than a separate issue.",
"CVSS AT:N is used because the only options are N or P; the attacker does perform active interaction (submitting a signed event), but no special passive observation position is required."
],
"capecRationale": [
{
"capecId": "CAPEC-124",
"rationale": "The revoked-key state is an exceptional condition in the key lifecycle that the application failed to handle correctly during signature validation and key synchronization. The attacker exploits the system\u0027s failure to treat a revoked key as an exceptional (invalid) state. This is the closest CAPEC pattern; a more specific \u0027key revocation bypass\u0027 pattern does not exist in the CAPEC catalog, so CAPEC-124 is the best available match."
},
{
"capecId": "CAPEC-100",
"rationale": "The key-sync path is vulnerable to manipulation of the pushed key list: by omitting keys or crafting entries without fingerprints, an attacker can prevent revocations from being applied or cause valid keys to be removed. This is a secondary attack vector enabled by the same code defects. The mapping is approximate because the primary issue is a logic flaw rather than direct parameter injection."
}
],
"commit": "eee1f8b675c5c472fa73b41982824c0c17dd639e",
"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 attacker interacts via the HTTP API. AC:L: exploitation requires only signing an event with a revoked key and submitting it; no race conditions or special timing. AT:N: no special targeting beyond network reachability to the MISP instance. PR:L: the attacker must be an authenticated sync user with permission to add/edit protected events. UI:N: no victim interaction is required. VC:N: no confidentiality impact is evident. VI:H: integrity is significantly impacted because revoked keys retain signing authority and revocations are not applied, undermining the trust chain for protected events. VA:N: the 500-error issue is minor and does not constitute a meaningful availability impact. SC:N: no secondary confidentiality impact. SI:H: in a multi-instance MISP sync network, events signed by revoked keys can propagate to peer instances, extending the integrity compromise. SA:N: no secondary availability impact.",
"draft": false,
"fixSummary": "The fix enforces key revocation in signature validation by skipping any key whose revoked flag is set before attempting PGP verification. It corrects the key-sync query to retrieve all stored keys (not just the first), ensures revocations are persisted and never lifted by a subsequent push, properly removes keys absent from the pushed list, and computes a fingerprint for entries that lack one so they match their stored counterpart. A signed protected event with no keys is now refused with a proper error response instead of an unhandled 500.",
"generatedAt": "2026-11-19T14:35:26.990914Z",
"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": "ad525a5a81462a3936cd6ad7cb153b93b23ec465ba010b8634cee54bcb6c7d87",
"patchSummary": "In CryptographicKey.php: (1) validateProtectedEvent() now checks $supplied_key[\u0027revoked\u0027] and continues (skips) if set, before calling verifySignature(). (2) captureCryptographicKeyUpdate() changes find(\u0027first\u0027) to find(\u0027all\u0027) so all stored keys are considered. (3) A pre-loop computes a fingerprint via extractKeyData() for pushed entries that lack one. (4) The revocation branch is restructured: it now saves only the revoked flag (id + revoked=1) and the condition uses !empty() checks to ensure a revocation is never lifted. (5) The $existingKey array access is flattened (removing the nested \u0027CryptographicKey\u0027 key). (6) deleteAll() is guarded with an empty check on $toRemove. (7) The no-keys error message includes the event UUID and the log entry uses event ID 0. In tests/testregressions.py: a new ProtectedEventKeyRevocation test class adds nine regression tests covering revoked-key rejection, unrevoked-key acceptance, revocation persistence, non-lifting of revocations, key removal, fingerprint-less entry match",
"patchTruncated": false,
"patches": [
{
"commit": "eee1f8b675c5c472fa73b41982824c0c17dd639e",
"date": "Sat, 14 Nov 2026 12:53:39 +0100",
"patchSha256": "ad525a5a81462a3936cd6ad7cb153b93b23ec465ba010b8634cee54bcb6c7d87",
"retrievedAt": "2026-11-19T14:34:41.330303Z",
"source": "https://github.com/MISP/MISP/commit/eee1f8b67.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/eee1f8b67.patch",
"subject": "fix: [security] Revoked keys no longer sign protected events,"
}
],
"source": "https://github.com/MISP/MISP/commit/eee1f8b67.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:35:26Z",
"version": "2.0.3"
},
"subject": "fix: [security] Revoked keys no longer sign protected events,",
"weaknessRationale": [
{
"cweId": "CWE-345",
"rationale": "The signature verification routine validated the cryptographic signature but failed to verify the authenticity/validity of the signing key by checking its revocation status. A revoked key was treated as a valid signing authority, which is a failure to fully verify data authenticity."
},
{
"cweId": "CWE-287",
"rationale": "The system accepted a revoked key as a valid credential for signing protected events, effectively failing to authenticate the signer\u0027s current authorization status. The key revocation mechanism was bypassed."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (eee1f8b675c5c472fa73b41982824c0c17dd639e): fix: [security] Revoked keys no longer sign protected events,",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/eee1f8b67.patch"
],
"timestamp": "2026-11-14T11:53:39Z",
"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/eee1f8b67.patch"
],
"timestamp": "2026-11-19T14:34:41.330303Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20236"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133190",
"datePublished": "2026-11-19T14:44:46.132Z",
"dateReserved": "2026-11-19T14:44:40.990Z",
"dateUpdated": "2026-11-19T14:52:25.872Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133188 (GCVE-0-2026-133188)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:32 – Updated: 2026-11-19 20:09qwen3.8:27b
4 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-19 14:26 - Model
qwen3.8:27b- Input
-
patch set (2 sources)
b81058778949… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
d5a3e9900708
|
fix: [security] Protected events refuse signed data with | bd22e66a2c32… |
18d0e9a77d0c
|
fix: [security] Protected events are signed over their exact | 4340f1f4d2e8… |
Fix summary
The vulnerability is remediated by (1) adding a post-signature-verification scan that rejects protected event bodies containing whitespace in JSON keys or identifier values, and (2) introducing an exact-byte PGP signature (x-pgp-signature-v2) that covers the body as transmitted without whitespace normalization. MISP 3.0+ peers use the exact-byte signature exclusively; older peers retain the legacy whitespace-stripped signature. A signature_version marker in the event body ensures that a 3.0 receiver refuses a legacy-only signature for events that were signed over exact bytes, preventing downgrade attacks.
Patch summary
Patch 1 (d5a3e9900) adds a private method __hasUnsignedWhitespace() to CryptographicKey that recursively scans decoded JSON for whitespace in string keys (excluding 'meta' sub-keys) and in values whose keys match identifier patterns (uuid, id, timestamp, distribution, date). validateProtectedEvent() now calls this check after a successful signature verification and returns false with a log entry if unsigned whitespace is found. Patch 2 (18d0e9a77) extends signWithInstanceKey() and verifySignature() with an $exact parameter that skips whitespace stripping. A new signatureHeaders() method selects the appropriate signature header(s) based on the peer's MISP version. EventsController, ServerSyncTool, and RestResponseComponent are updated to emit and consume the x-pgp-signature-v2 header. The signature_version field is injected into protected event bodies. Server.php passes the v2 header to validateProtectedEvent(). A new test file ProtectedEventExactSignatureTest.php (339 lines) covers acceptance, rejection, and
CVSS rationale
AV:N: The attacker operates over the network, intercepting and modifying traffic between MISP instances. AC:L: Inserting whitespace characters into JSON is a simple, deterministic transformation requiring no special conditions. AT:N: The target does not need to be in a particular state; any protected event in transit is vulnerable. PR:N: The attacker does not require authentication to the MISP instance; a network relay position suffices. UI:N: No user interaction is required; the tampered event is processed automatically. VC:N: No confidentiality impact; the attack modifies data, not exposes it. VI:H: The attacker can rename JSON fields and alter identifier values (UUIDs, timestamps), changing the semantic meaning of protected events while the signature still validates. VA:N: No availability impact. SC:N, SI:N, SA:N: The impact is confined to the receiving MISP instance's data integrity; no cross-scope or availability effects are evidenced.
Weakness rationale
- CWE-347 The PGP signature was computed and verified over a whitespace-stripped representation of the JSON body rather than the exact bytes transmitted. This allowed an attacker to modify the data (by inserting whitespace into keys or identifiers) without invalidating the signature, constituting an improper verification of the cryptographic signature's coverage.
- CWE-345 The signature verification mechanism did not fully ensure the authenticity of the received data because the normalization step (whitespace removal) created a gap between the signed representation and the actual data, allowing undetected modifications.
Attack pattern rationale
- CAPEC-126 The digital signature mechanism was implemented over a normalized (whitespace-stripped) representation of the data rather than the exact transmitted bytes. An attacker in a relay position exploits this by inserting whitespace into JSON keys or identifier values, which survives the normalization and thus the signature check. CAPEC-126 is the closest match; uncertainty exists because the CAPEC catalog does not have a more specific pattern for signature-coverage gaps introduced by data normalization.
Assumptions to verify
- The CAPEC-126 mapping is the closest available pattern; the CAPEC catalog lacks a more specific entry for signature-coverage gaps introduced by data normalization before signing.
- CVSS PR:N assumes the attacker only needs a network relay position and does not require authentication to either MISP instance; if the deployment requires authenticated relay, PR would be elevated.
- CVSS VI:H assumes that renaming JSON fields or altering timestamps in protected events constitutes a high integrity impact; if the specific deployment treats these fields as non-critical, VI could be L.
- The affected version boundary (< 3.0.0) is inferred from the patch's version_compare logic; the exact last affected release is not stated in the patch.
- The Galaxy cluster 'meta' key exclusion from the whitespace scan means whitespace in meta keys remains a residual (documented) limitation, not a vulnerability.
- SSVC technical_impact is set to 'partial' as the attacker can only insert whitespace, not arbitrarily rewrite event content; if field renaming has critical downstream effects in a specific deployment, 'total' may be more appropriate.
- The Co-Authored-By line credits an AI assistant (Claude Opus 5.5); inclusion as a remediation developer follows the explicit metadata but is atypical for CVE credit conventions.
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-13 11:25 UTC Fix developed Corrective change authored (d5a3e9900708e409bc9c517c57aa819883ca879e): fix: [security] Protected events refuse signed data with https://github.com/MISP/MISP/commit/d5a3e9900.patch
- 2026-11-17 13:37 UTC Fix developed Corrective change authored (18d0e9a77d0c1d790a1742d9d886bf033d303ac6): fix: [security] Protected events are signed over their exact https://github.com/MISP/MISP/commit/18d0e9a77.patch
- 2026-11-19 14:25 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/d5a3e9900.patch
- 2026-11-19 14:25 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/18d0e9a77.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133188",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T20:08:55.828367Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T20:09:05.870Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"app/Model/CryptographicKey.php",
"app/Controller/EventsController.php",
"app/Lib/Tools/ServerSyncTool.php",
"app/Model/Server.php",
"app/Controller/Component/RestResponseComponent.php"
],
"product": "misp",
"programFiles": [],
"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"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
}
],
"descriptions": [
{
"lang": "en",
"value": "MISP contains a vulnerability in the cryptographic signature verification of protected events. When a MISP instance signs a protected event for synchronization, it strips all whitespace from the JSON body before computing the PGP signature (preg_replace(\"/\\s+/\", \"\", $data)). The receiving instance performs the same whitespace-stripping before verification. Because the signature covers only the whitespace-free representation, a network relay positioned between two MISP instances can insert whitespace characters into JSON object keys (effectively renaming fields) or into identifier values such as UUIDs, timestamps, and distribution fields without invalidating the signature. The receiving instance accepts the modified event as authentic.\n\nThe vulnerability affects the protected event synchronization path: event creation (EventsController::add), event editing (EventsController::edit), event viewing (EventsController::view1), and server-to-server pull synchronization (ServerSyncTool, Server model). An attacker with a network position to intercept and modify traffic between MISP instances can alter the semantic content of protected events while the PGP signature still validates, undermining the integrity guarantees that protected events are designed to provide.\n\nThe fix introduces two complementary mechanisms. First, a post-verification scan rejects any received body that contains whitespace in JSON keys (except under Galaxy cluster \u0027meta\u0027 keys) or in identifier-like values (uuid, id, timestamp, distribution, date). Second, a new exact-byte signature scheme (x-pgp-signature-v2) signs the body as transmitted, without whitespace normalization. MISP 3.0 and later peers exchange this exact-byte signature; older peers retain the legacy whitespace-stripped signature. A signature_version field is embedded in protected events so that a 3.0 receiver refuses a body carrying that marker if only the legacy signature is present. Both mechanisms together close the whitespace-injection vector while preserving backward compatibility with pre-3.0 instances."
}
],
"impacts": [
{
"capecId": "CAPEC-126",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-126 Exploiting Incorrectly Implemented Digital Signatures"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 6.9,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW",
"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-19T14:26:06Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-347",
"description": "CWE-347 Improper Verification of Cryptographic Signature",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-345",
"description": "CWE-345 Insufficient Verification of Data Authenticity",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:32:35.724Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/d5a3e9900"
},
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/18d0e9a77"
}
],
"solutions": [
{
"lang": "en",
"value": "The vulnerability is remediated by (1) adding a post-signature-verification scan that rejects protected event bodies containing whitespace in JSON keys or identifier values, and (2) introducing an exact-byte PGP signature (x-pgp-signature-v2) that covers the body as transmitted without whitespace normalization. MISP 3.0+ peers use the exact-byte signature exclusively; older peers retain the legacy whitespace-stripped signature. A signature_version marker in the event body ensures that a 3.0 receiver refuses a legacy-only signature for events that were signed over exact bytes, preventing downgrade attacks."
}
],
"title": "MISP Protected Event Signature Bypass via Whitespace Injection in JSON Keys and Identifiers",
"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 CAPEC-126 mapping is the closest available pattern; the CAPEC catalog lacks a more specific entry for signature-coverage gaps introduced by data normalization before signing.",
"CVSS PR:N assumes the attacker only needs a network relay position and does not require authentication to either MISP instance; if the deployment requires authenticated relay, PR would be elevated.",
"CVSS VI:H assumes that renaming JSON fields or altering timestamps in protected events constitutes a high integrity impact; if the specific deployment treats these fields as non-critical, VI could be L.",
"The affected version boundary (\u003c 3.0.0) is inferred from the patch\u0027s version_compare logic; the exact last affected release is not stated in the patch.",
"The Galaxy cluster \u0027meta\u0027 key exclusion from the whitespace scan means whitespace in meta keys remains a residual (documented) limitation, not a vulnerability.",
"SSVC technical_impact is set to \u0027partial\u0027 as the attacker can only insert whitespace, not arbitrarily rewrite event content; if field renaming has critical downstream effects in a specific deployment, \u0027total\u0027 may be more appropriate.",
"The Co-Authored-By line credits an AI assistant (Claude Opus 5.5); inclusion as a remediation developer follows the explicit metadata but is atypical for CVE credit conventions."
],
"capecRationale": [
{
"capecId": "CAPEC-126",
"rationale": "The digital signature mechanism was implemented over a normalized (whitespace-stripped) representation of the data rather than the exact transmitted bytes. An attacker in a relay position exploits this by inserting whitespace into JSON keys or identifier values, which survives the normalization and thus the signature check. CAPEC-126 is the closest match; uncertainty exists because the CAPEC catalog does not have a more specific pattern for signature-coverage gaps introduced by data normalization."
}
],
"commit": "18d0e9a77d0c1d790a1742d9d886bf033d303ac6",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
}
],
"cvssRationale": "AV:N: The attacker operates over the network, intercepting and modifying traffic between MISP instances. AC:L: Inserting whitespace characters into JSON is a simple, deterministic transformation requiring no special conditions. AT:N: The target does not need to be in a particular state; any protected event in transit is vulnerable. PR:N: The attacker does not require authentication to the MISP instance; a network relay position suffices. UI:N: No user interaction is required; the tampered event is processed automatically. VC:N: No confidentiality impact; the attack modifies data, not exposes it. VI:H: The attacker can rename JSON fields and alter identifier values (UUIDs, timestamps), changing the semantic meaning of protected events while the signature still validates. VA:N: No availability impact. SC:N, SI:N, SA:N: The impact is confined to the receiving MISP instance\u0027s data integrity; no cross-scope or availability effects are evidenced.",
"draft": false,
"fixSummary": "The vulnerability is remediated by (1) adding a post-signature-verification scan that rejects protected event bodies containing whitespace in JSON keys or identifier values, and (2) introducing an exact-byte PGP signature (x-pgp-signature-v2) that covers the body as transmitted without whitespace normalization. MISP 3.0+ peers use the exact-byte signature exclusively; older peers retain the legacy whitespace-stripped signature. A signature_version marker in the event body ensures that a 3.0 receiver refuses a legacy-only signature for events that were signed over exact bytes, preventing downgrade attacks.",
"generatedAt": "2026-11-19T14:26:06.814235Z",
"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": "b81058778949ad6e64fefc78c4a9806e7776068075a40a338d47eb1d26eafde6",
"patchSummary": "Patch 1 (d5a3e9900) adds a private method __hasUnsignedWhitespace() to CryptographicKey that recursively scans decoded JSON for whitespace in string keys (excluding \u0027meta\u0027 sub-keys) and in values whose keys match identifier patterns (uuid, id, timestamp, distribution, date). validateProtectedEvent() now calls this check after a successful signature verification and returns false with a log entry if unsigned whitespace is found.\n\nPatch 2 (18d0e9a77) extends signWithInstanceKey() and verifySignature() with an $exact parameter that skips whitespace stripping. A new signatureHeaders() method selects the appropriate signature header(s) based on the peer\u0027s MISP version. EventsController, ServerSyncTool, and RestResponseComponent are updated to emit and consume the x-pgp-signature-v2 header. The signature_version field is injected into protected event bodies. Server.php passes the v2 header to validateProtectedEvent(). A new test file ProtectedEventExactSignatureTest.php (339 lines) covers acceptance, rejection, and",
"patchTruncated": false,
"patches": [
{
"commit": "d5a3e9900708e409bc9c517c57aa819883ca879e",
"date": "Fri, 13 Nov 2026 12:25:34 +0100",
"patchSha256": "bd22e66a2c3212896f9b0c25657a4e3d2e47ff2ba6bd377d33b4b62b2c524e08",
"retrievedAt": "2026-11-19T14:25:13.678489Z",
"source": "https://github.com/MISP/MISP/commit/d5a3e9900.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/d5a3e9900.patch",
"subject": "fix: [security] Protected events refuse signed data with"
},
{
"commit": "18d0e9a77d0c1d790a1742d9d886bf033d303ac6",
"date": "Tue, 17 Nov 2026 14:37:58 +0100",
"patchSha256": "4340f1f4d2e8a9f0806650a0896c11c11533e3d6ec6df786707ecdf2fd8120a5",
"retrievedAt": "2026-11-19T14:25:13.961710Z",
"source": "https://github.com/MISP/MISP/commit/18d0e9a77.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/18d0e9a77.patch",
"subject": "fix: [security] Protected events are signed over their exact"
}
],
"source": "patch set (2 sources)",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:26:06Z",
"version": "2.0.3"
},
"subject": "fix: [security] Protected events are signed over their exact",
"weaknessRationale": [
{
"cweId": "CWE-347",
"rationale": "The PGP signature was computed and verified over a whitespace-stripped representation of the JSON body rather than the exact bytes transmitted. This allowed an attacker to modify the data (by inserting whitespace into keys or identifiers) without invalidating the signature, constituting an improper verification of the cryptographic signature\u0027s coverage."
},
{
"cweId": "CWE-345",
"rationale": "The signature verification mechanism did not fully ensure the authenticity of the received data because the normalization step (whitespace removal) created a gap between the signed representation and the actual data, allowing undetected modifications."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (d5a3e9900708e409bc9c517c57aa819883ca879e): fix: [security] Protected events refuse signed data with",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/d5a3e9900.patch"
],
"timestamp": "2026-11-13T11:25:34Z",
"type": "fix-developed"
},
{
"description": "Corrective change authored (18d0e9a77d0c1d790a1742d9d886bf033d303ac6): fix: [security] Protected events are signed over their exact",
"id": "evt-fix-developed-2",
"references": [
"https://github.com/MISP/MISP/commit/18d0e9a77.patch"
],
"timestamp": "2026-11-17T13:37:58Z",
"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/d5a3e9900.patch"
],
"timestamp": "2026-11-19T14:25:13.678489Z",
"type": "fix-available"
},
{
"description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
"id": "evt-fix-available-2",
"references": [
"https://github.com/MISP/MISP/commit/18d0e9a77.patch"
],
"timestamp": "2026-11-19T14:25:13.961710Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20342"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133188",
"datePublished": "2026-11-19T14:32:35.724Z",
"dateReserved": "2026-11-19T14:32:32.740Z",
"dateUpdated": "2026-11-19T20:09:05.870Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133184 (GCVE-0-2026-133184)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:23 – Updated: 2026-11-19 20:07| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/0a60e142b | 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-19 14:21 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/0a60e142b.patch
393b70d07120… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
0a60e142b048
|
fix: [security] A push target only picks from the events | 393b70d07120… |
Fix summary
The fix enforces three security controls in the push path: (1) an explicit check that the event's 'published' flag is set before the event is eligible for push, returning a descriptive error if it is not; (2) a guard that skips any event for which the pushing user's fetch returns empty, preventing transmission of inaccessible events as empty shells; and (3) validation of the remote server's event-selection reply so that only UUIDs present in the originally offered event list are accepted, discarding any identifiers the remote references that were not part of the push offer.
Patch summary
In app/Model/Event.php, a new early-return check is added at the top of uploadEventToServer() that rejects the push if $event['Event']['published'] is empty. In app/Model/Server.php, three changes are made: (a) in the push() loop, a 'continue' statement is added when fetchEvent() returns empty, skipping inaccessible events; (b) the lastpushedid fallback logic is corrected to preserve the existing value when both successes and fails are empty; (c) in getEventIdsForPush(), the remote's JSON reply is validated as an array, filtered to string values, and then cross-referenced against the UUIDs in the $request (offered events) array so that only UUIDs present in both sets are returned.
CVSS rationale
AV:N: The push occurs over the network between MISP instances. AC:L: Triggering a push is a standard user action with no special race or timing conditions. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with push permissions is required. UI:N: No additional user interaction beyond initiating the push. VC:L: Confidential event data (unpublished events, events the user cannot access) is disclosed to the remote server. VI:N, VA:N: No integrity or availability impact on the source. SC:N, SI:N, SA:N: The remote server receives data but its own confidentiality, integrity, and availability are not compromised.
Weakness rationale
- CWE-862 The push mechanism does not enforce that events are published or that the pushing user has read access before transmitting them to a remote server, constituting a missing authorization check on data egress.
- CWE-20 The remote server's reply selecting events to accept is used without validating that the referenced identifiers belong to the set of events actually offered in the push request, allowing out-of-scope references.
Attack pattern rationale
- CAPEC-126 The MISP push mechanism relies on a trusted relationship between the source and remote MISP instances. The source trusts the push flow and the remote's reply without enforcing proper authorization (published status, user access) or validating the remote's selection against the offered set. The closest CAPEC is Leverage Trusted Relationship because the vulnerability arises from insufficient validation within a trusted inter-system data exchange. Uncertainty: no CAPEC perfectly captures 'missing authorization on outbound data push'; CAPEC-126 is the best available match for a trusted-relationship data-flow flaw.
Assumptions to verify
- The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.
- PR:L assumes the attacker needs a standard authenticated user with push permissions; if push is restricted to administrators only, PR could be H.
- VC:L assumes the disclosed data (unpublished events, inaccessible event metadata) constitutes a low confidentiality impact; if the events contain highly sensitive threat intelligence, the impact could be higher.
- CAPEC-126 is the closest available mapping; no CAPEC precisely describes 'missing authorization on outbound data push in a trusted inter-system exchange.'
- The remote server's ability to reference non-offered events (CWE-20 component) is assessed as low impact because the events would still need to exist and be accessible on the source; the primary impact is the authorization bypass (CWE-862).
- The 'Co-Authored-By: Claude Opus 5.5' credit is included as listed in the commit metadata; its role as a remediation developer is inferred from the co-authorship line.
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-13 09:02 UTC Fix developed Corrective change authored (0a60e142b048513ef48a103ef15ae56e3b679e0e): fix: [security] A push target only picks from the events https://github.com/MISP/MISP/commit/0a60e142b.patch
- 2026-11-19 14:20 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/0a60e142b.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133184",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T20:06:48.582946Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T20:07:07.998Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"Event model (uploadEventToServer)",
"Server model (push, getEventIdsForPush)"
],
"product": "misp",
"programFiles": [
"app/Model/Event.php",
"app/Model/Server.php"
],
"repo": "https://github.com/MISP/MISP",
"vendor": "misp",
"versions": [
{
"lessThanOrEqual": "2.5.51",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.5.51",
"versionStartIncluding": "0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
}
],
"descriptions": [
{
"lang": "en",
"value": "MISP contains an authorization and input-validation flaw in its event push mechanism. When a user with push permissions initiates a push of events to a remote MISP instance, the system fails to enforce two critical checks: (1) it does not verify that an event is published before including it in the push, allowing unpublished (i.e., not yet publicly shared) events to be transmitted to the remote server; and (2) it does not verify that the pushing user has read access to the event, causing events the user cannot fetch to be sent as empty event shells, thereby disclosing the existence and metadata of events the user is not authorized to view. Additionally, the remote server\u0027s reply selecting which offered events to accept is used without validating that the selected identifiers actually correspond to events in the offered set, potentially allowing the remote to reference events outside the intended scope. The vulnerability requires an authenticated user with push permissions on the source MISP instance and a configured push target. The security impact is unauthorized disclosure of confidential threat-intelligence data (unpublished events and events restricted by user permissions) to a remote MISP instance that should not receive them."
}
],
"impacts": [
{
"capecId": "CAPEC-126",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-126 Leverage Trusted Relationship"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:21:31Z",
"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-20",
"description": "CWE-20 Improper Input Validation",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:23:36.482Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/0a60e142b"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix enforces three security controls in the push path: (1) an explicit check that the event\u0027s \u0027published\u0027 flag is set before the event is eligible for push, returning a descriptive error if it is not; (2) a guard that skips any event for which the pushing user\u0027s fetch returns empty, preventing transmission of inaccessible events as empty shells; and (3) validation of the remote server\u0027s event-selection reply so that only UUIDs present in the originally offered event list are accepted, discarding any identifiers the remote references that were not part of the push offer."
}
],
"title": "MISP Push Mechanism Discloses Unpublished and Inaccessible Events to Remote Server",
"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 are assumed affected.",
"PR:L assumes the attacker needs a standard authenticated user with push permissions; if push is restricted to administrators only, PR could be H.",
"VC:L assumes the disclosed data (unpublished events, inaccessible event metadata) constitutes a low confidentiality impact; if the events contain highly sensitive threat intelligence, the impact could be higher.",
"CAPEC-126 is the closest available mapping; no CAPEC precisely describes \u0027missing authorization on outbound data push in a trusted inter-system exchange.\u0027",
"The remote server\u0027s ability to reference non-offered events (CWE-20 component) is assessed as low impact because the events would still need to exist and be accessible on the source; the primary impact is the authorization bypass (CWE-862).",
"The \u0027Co-Authored-By: Claude Opus 5.5\u0027 credit is included as listed in the commit metadata; its role as a remediation developer is inferred from the co-authorship line."
],
"capecRationale": [
{
"capecId": "CAPEC-126",
"rationale": "The MISP push mechanism relies on a trusted relationship between the source and remote MISP instances. The source trusts the push flow and the remote\u0027s reply without enforcing proper authorization (published status, user access) or validating the remote\u0027s selection against the offered set. The closest CAPEC is Leverage Trusted Relationship because the vulnerability arises from insufficient validation within a trusted inter-system data exchange. Uncertainty: no CAPEC perfectly captures \u0027missing authorization on outbound data push\u0027; CAPEC-126 is the best available match for a trusted-relationship data-flow flaw."
}
],
"commit": "0a60e142b048513ef48a103ef15ae56e3b679e0e",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
}
],
"cvssRationale": "AV:N: The push occurs over the network between MISP instances. AC:L: Triggering a push is a standard user action with no special race or timing conditions. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with push permissions is required. UI:N: No additional user interaction beyond initiating the push. VC:L: Confidential event data (unpublished events, events the user cannot access) is disclosed to the remote server. VI:N, VA:N: No integrity or availability impact on the source. SC:N, SI:N, SA:N: The remote server receives data but its own confidentiality, integrity, and availability are not compromised.",
"draft": false,
"fixSummary": "The fix enforces three security controls in the push path: (1) an explicit check that the event\u0027s \u0027published\u0027 flag is set before the event is eligible for push, returning a descriptive error if it is not; (2) a guard that skips any event for which the pushing user\u0027s fetch returns empty, preventing transmission of inaccessible events as empty shells; and (3) validation of the remote server\u0027s event-selection reply so that only UUIDs present in the originally offered event list are accepted, discarding any identifiers the remote references that were not part of the push offer.",
"generatedAt": "2026-11-19T14:21:31.586210Z",
"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": "393b70d07120c4546bc6153eaa230f99a917884232801c0502a22fa869ce5b9b",
"patchSummary": "In app/Model/Event.php, a new early-return check is added at the top of uploadEventToServer() that rejects the push if $event[\u0027Event\u0027][\u0027published\u0027] is empty. In app/Model/Server.php, three changes are made: (a) in the push() loop, a \u0027continue\u0027 statement is added when fetchEvent() returns empty, skipping inaccessible events; (b) the lastpushedid fallback logic is corrected to preserve the existing value when both successes and fails are empty; (c) in getEventIdsForPush(), the remote\u0027s JSON reply is validated as an array, filtered to string values, and then cross-referenced against the UUIDs in the $request (offered events) array so that only UUIDs present in both sets are returned.",
"patchTruncated": false,
"patches": [
{
"commit": "0a60e142b048513ef48a103ef15ae56e3b679e0e",
"date": "Fri, 13 Nov 2026 10:02:39 +0100",
"patchSha256": "393b70d07120c4546bc6153eaa230f99a917884232801c0502a22fa869ce5b9b",
"retrievedAt": "2026-11-19T14:20:49.401797Z",
"source": "https://github.com/MISP/MISP/commit/0a60e142b.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/0a60e142b.patch",
"subject": "fix: [security] A push target only picks from the events"
}
],
"source": "https://github.com/MISP/MISP/commit/0a60e142b.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:21:31Z",
"version": "2.0.3"
},
"subject": "fix: [security] A push target only picks from the events",
"weaknessRationale": [
{
"cweId": "CWE-862",
"rationale": "The push mechanism does not enforce that events are published or that the pushing user has read access before transmitting them to a remote server, constituting a missing authorization check on data egress."
},
{
"cweId": "CWE-20",
"rationale": "The remote server\u0027s reply selecting events to accept is used without validating that the referenced identifiers belong to the set of events actually offered in the push request, allowing out-of-scope references."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (0a60e142b048513ef48a103ef15ae56e3b679e0e): fix: [security] A push target only picks from the events",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/0a60e142b.patch"
],
"timestamp": "2026-11-13T09:02:39Z",
"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/0a60e142b.patch"
],
"timestamp": "2026-11-19T14:20:49.401797Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20330"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133184",
"datePublished": "2026-11-19T14:23:36.482Z",
"dateReserved": "2026-11-19T14:23:32.867Z",
"dateUpdated": "2026-11-19T20:07:07.998Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133183 (GCVE-0-2026-133183)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:19 – Updated: 2026-11-19 14:44- CWE-862 - Missing Authorization
| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/389ce674c | 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-19 14:13 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/389ce674c.patch
74f3a4178ae1… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
389ce674c1f8
|
fix: [security] Pulls and feeds no longer update sharing | 74f3a4178ae1… |
Fix summary
The fix introduces a proper authorization check for remote capture operations. The captureRemote method now receives the full server context (or null for feeds) and stores both the internal flag and the remote organization identifier. A new __remoteMayUpdate method verifies that, for non-internal pulls, the remote organization is a member of the target sharing group (as owning org, in the SharingGroupOrg list, or via an all_orgs entry). For feeds (server is null), the update is always refused. When the check fails, the sharing group record is left unchanged while the pulled data still attaches to it, preserving data integrity without granting unauthorized metadata modification.
Patch summary
Three files are modified. In Feed.php, two calls to SharingGroup::captureRemote change the first argument from false to null, indicating a feed has no server context. In Server.php, the pull method now passes the full $server array instead of a derived boolean. In SharingGroup.php, the static $remoteCapture variable changes from a boolean to an associative array holding internal (bool) and remote_org_id (int|null). The captureRemote method signature changes from accepting a bool to accepting an array or null. A new private method __remoteMayUpdate is added, which returns true for internal links, and for non-internal links checks that remote_org_id is set, the group is not local, and the remote org matches the group's org_id, appears in SharingGroupOrg, or is covered by an all_orgs SharingGroupServer entry. In captureSGExisting, a guard clause is inserted before the existing update logic: if a remote capture is active and __remoteMayUpdate returns false, the method returns the existing group id without further
CVSS rationale
AV:N: MISP is a network-accessible web application; pulls and feeds are initiated over HTTP. AC:L: An attacker with a configured pull or feed simply triggers the operation; no race conditions or special timing are needed. AT:N: No manipulation of the attack target is required. PR:L: The attacker must be an authenticated user with sync or feed privileges to initiate a pull or feed. UI:N: No victim interaction is required; the operation runs server-side. VC:N: No confidentiality impact is evident from the patch. VI:L: The integrity impact is limited to sharing group metadata (local flag, modified timestamp, org associations) being altered by an unauthorized remote entity. VA:N: No availability impact. SC:N/SI:N/SA:N: No evidence of impact on other systems; the modification is confined to the local MISP instance's sharing group record. SI is set to N rather than L because the patch does not demonstrate that the metadata change propagates to or alters the behavior of connected MISP instances; this is an assumption recorded below.
Weakness rationale
- CWE-862 The application failed to verify that the remote server's organization was a member of the target sharing group before permitting metadata updates during pull and feed operations. The authorization check was simply absent for the non-internal remote case; only a boolean internal flag was stored and checked, with no membership validation.
Attack pattern rationale
- CAPEC-114 The remote sync user or feed process is granted the ability to modify sharing group metadata beyond what its organizational membership should permit. The authorization logic incorrectly treats any non-internal remote capture as having the same update rights as an internal one, or fails to distinguish between a remote entity that is a group member and one that is not. This is the closest CAPEC pattern to an authorization-logic flaw where the privilege boundary is miscalculated. Uncertainty: no CAPEC pattern precisely describes 'missing membership check on a shared resource update'; CAPEC-114 is selected as the best available match for an incorrectly scoped privilege.
Assumptions to verify
- The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.
- The PR:L assumption assumes the attacker must be an authenticated user with sync or feed privileges; the patch does not explicitly state the minimum role required.
- SI:N assumes that modifying a local sharing group's metadata does not propagate integrity changes to remote MISP instances; the patch does not provide evidence of cross-instance impact.
- The CAPEC-114 mapping is the closest available pattern; no CAPEC precisely describes a missing membership-authorization check on a shared resource update.
- The patch commit date is 2026-11-12; the actual release timeline and fixed version are unknown.
- The Co-Authored-By line credits 'Claude Opus 5.5' as a remediation developer; this is recorded as-is from the commit metadata without independent verification.
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-12 11:53 UTC Fix developed Corrective change authored (389ce674c1f8596f247bccb76a35669da691bc3c): fix: [security] Pulls and feeds no longer update sharing https://github.com/MISP/MISP/commit/389ce674c.patch
- 2026-11-19 14:12 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/389ce674c.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133183",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:44:37.881472Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:44:47.659Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"app/Model/Feed.php",
"app/Model/Server.php",
"app/Model/SharingGroup.php"
],
"product": "misp",
"programFiles": [
"app/Model/Feed.php",
"app/Model/Server.php",
"app/Model/SharingGroup.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"
},
{
"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 handling of remote pull and feed operations. When a non-internal pull or a feed processes incoming data and encounters an existing sharing group, the application did not verify that the remote server\u0027s organization was actually a member of that sharing group before allowing the group\u0027s metadata to be updated. The captureRemote mechanism previously stored only a boolean flag indicating whether the link was internal, and the authorization check in captureSGExisting relied solely on that flag. For non-internal pulls and feeds, the check was insufficient: a remote server whose organization was not a member of the target sharing group could still cause the group record to be modified (for example, altering the local flag, the modified timestamp, or other group properties). A feed, which has no associated server organization at all, could likewise trigger an update to an existing sharing group\u0027s metadata. The security impact is an integrity violation: an authenticated remote entity with sync or feed privileges can alter sharing group attributes that govern how data is distributed among organizations, potentially changing the local flag or other access-relevant properties of groups it does not belong to. The vulnerability requires an authenticated user with the ability to initiate a pull or feed (a sync user or feed administrator) and a target sharing group that exists on the local instance. No unauthenticated access or user interaction is required."
}
],
"impacts": [
{
"capecId": "CAPEC-114",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-114 Exploiting Incorrectly Adjusted Privileges"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW",
"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-19T14:13:05Z",
"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"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:19:33.623Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/389ce674c"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix introduces a proper authorization check for remote capture operations. The captureRemote method now receives the full server context (or null for feeds) and stores both the internal flag and the remote organization identifier. A new __remoteMayUpdate method verifies that, for non-internal pulls, the remote organization is a member of the target sharing group (as owning org, in the SharingGroupOrg list, or via an all_orgs entry). For feeds (server is null), the update is always refused. When the check fails, the sharing group record is left unchanged while the pulled data still attaches to it, preserving data integrity without granting unauthorized metadata modification."
}
],
"title": "MISP: Remote Pull and Feed Operations Can Modify Sharing Group Metadata Without Organization Membership",
"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 are assumed affected.",
"The PR:L assumption assumes the attacker must be an authenticated user with sync or feed privileges; the patch does not explicitly state the minimum role required.",
"SI:N assumes that modifying a local sharing group\u0027s metadata does not propagate integrity changes to remote MISP instances; the patch does not provide evidence of cross-instance impact.",
"The CAPEC-114 mapping is the closest available pattern; no CAPEC precisely describes a missing membership-authorization check on a shared resource update.",
"The patch commit date is 2026-11-12; the actual release timeline and fixed version are unknown.",
"The Co-Authored-By line credits \u0027Claude Opus 5.5\u0027 as a remediation developer; this is recorded as-is from the commit metadata without independent verification."
],
"capecRationale": [
{
"capecId": "CAPEC-114",
"rationale": "The remote sync user or feed process is granted the ability to modify sharing group metadata beyond what its organizational membership should permit. The authorization logic incorrectly treats any non-internal remote capture as having the same update rights as an internal one, or fails to distinguish between a remote entity that is a group member and one that is not. This is the closest CAPEC pattern to an authorization-logic flaw where the privilege boundary is miscalculated. Uncertainty: no CAPEC pattern precisely describes \u0027missing membership check on a shared resource update\u0027; CAPEC-114 is selected as the best available match for an incorrectly scoped privilege."
}
],
"commit": "389ce674c1f8596f247bccb76a35669da691bc3c",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
}
],
"cvssRationale": "AV:N: MISP is a network-accessible web application; pulls and feeds are initiated over HTTP. AC:L: An attacker with a configured pull or feed simply triggers the operation; no race conditions or special timing are needed. AT:N: No manipulation of the attack target is required. PR:L: The attacker must be an authenticated user with sync or feed privileges to initiate a pull or feed. UI:N: No victim interaction is required; the operation runs server-side. VC:N: No confidentiality impact is evident from the patch. VI:L: The integrity impact is limited to sharing group metadata (local flag, modified timestamp, org associations) being altered by an unauthorized remote entity. VA:N: No availability impact. SC:N/SI:N/SA:N: No evidence of impact on other systems; the modification is confined to the local MISP instance\u0027s sharing group record. SI is set to N rather than L because the patch does not demonstrate that the metadata change propagates to or alters the behavior of connected MISP instances; this is an assumption recorded below.",
"draft": false,
"fixSummary": "The fix introduces a proper authorization check for remote capture operations. The captureRemote method now receives the full server context (or null for feeds) and stores both the internal flag and the remote organization identifier. A new __remoteMayUpdate method verifies that, for non-internal pulls, the remote organization is a member of the target sharing group (as owning org, in the SharingGroupOrg list, or via an all_orgs entry). For feeds (server is null), the update is always refused. When the check fails, the sharing group record is left unchanged while the pulled data still attaches to it, preserving data integrity without granting unauthorized metadata modification.",
"generatedAt": "2026-11-19T14:13:05.024627Z",
"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": "74f3a4178ae1a24dd5531603002bccc8c0a264433e471b42803927e4d77b77e4",
"patchSummary": "Three files are modified. In Feed.php, two calls to SharingGroup::captureRemote change the first argument from false to null, indicating a feed has no server context. In Server.php, the pull method now passes the full $server array instead of a derived boolean. In SharingGroup.php, the static $remoteCapture variable changes from a boolean to an associative array holding internal (bool) and remote_org_id (int|null). The captureRemote method signature changes from accepting a bool to accepting an array or null. A new private method __remoteMayUpdate is added, which returns true for internal links, and for non-internal links checks that remote_org_id is set, the group is not local, and the remote org matches the group\u0027s org_id, appears in SharingGroupOrg, or is covered by an all_orgs SharingGroupServer entry. In captureSGExisting, a guard clause is inserted before the existing update logic: if a remote capture is active and __remoteMayUpdate returns false, the method returns the existing group id without further",
"patchTruncated": false,
"patches": [
{
"commit": "389ce674c1f8596f247bccb76a35669da691bc3c",
"date": "Thu, 12 Nov 2026 12:53:40 +0100",
"patchSha256": "74f3a4178ae1a24dd5531603002bccc8c0a264433e471b42803927e4d77b77e4",
"retrievedAt": "2026-11-19T14:12:22.958245Z",
"source": "https://github.com/MISP/MISP/commit/389ce674c.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/389ce674c.patch",
"subject": "fix: [security] Pulls and feeds no longer update sharing"
}
],
"source": "https://github.com/MISP/MISP/commit/389ce674c.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:13:05Z",
"version": "2.0.3"
},
"subject": "fix: [security] Pulls and feeds no longer update sharing",
"weaknessRationale": [
{
"cweId": "CWE-862",
"rationale": "The application failed to verify that the remote server\u0027s organization was a member of the target sharing group before permitting metadata updates during pull and feed operations. The authorization check was simply absent for the non-internal remote case; only a boolean internal flag was stored and checked, with no membership validation."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (389ce674c1f8596f247bccb76a35669da691bc3c): fix: [security] Pulls and feeds no longer update sharing",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/389ce674c.patch"
],
"timestamp": "2026-11-12T11:53:40Z",
"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/389ce674c.patch"
],
"timestamp": "2026-11-19T14:12:22.958245Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20268"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133183",
"datePublished": "2026-11-19T14:19:33.623Z",
"dateReserved": "2026-11-19T14:19:30.159Z",
"dateUpdated": "2026-11-19T14:44:47.659Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133178 (GCVE-0-2026-133178)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:11 – Updated: 2026-11-19 14:46| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/ade… | 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 14:21 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch
5c27997cbe9f… - Confidence
- high
| Commit | Subject | Patch SHA-256 |
|---|---|---|
adef89f5c827
|
fix: [security] Neutralise formulas in case and task CSV | 5c27997cbe9f… |
Fix summary
A shared CSV cell formatter (csv_safe_cell) is introduced that detects formula-like strings—those beginning with =, +, -, @, their fullwidth Unicode variants, or leading control/whitespace characters—and prefixes them with an apostrophe so spreadsheet applications treat the content as literal text. All case and task CSV export rows now pass every cell value through this formatter before writing, while numeric and ordinary text values are left unchanged.
Patch summary
New file app/utils/csv_utils.py defines csv_safe_cell(value) which returns an empty string for None, prepends an apostrophe to strings that start with tab/CR/LF or whose lstrip()-ed form begins with =, +, -, @, or fullwidth equivalents (=, +, -, @), and otherwise returns the value unchanged. In app/tools/tools.py the _cases_to_csv function is modified so that both case rows and task rows are wrapped with a dict comprehension applying csv_safe_cell to every field before writer.writerow. The user manual (doc/user-manual.md) gains a note explaining the apostrophe-prefixing behaviour and that JSON exports preserve original text.
CVSS rationale
AV:N – exploitation occurs over the network via the web interface. AC:L – crafting formula-like text requires no special conditions. AT:N – no specific attack prerequisites. PR:L – the attacker needs editor-level access to create or modify case/task fields. UI:A – the victim must actively open the CSV in a spreadsheet application for the formula to execute. VC/VI/VA:N – the primary system (flowintel) suffers no direct confidentiality, integrity, or availability impact. SC:L – the secondary system (spreadsheet) may leak data via formula functions. SI:L – the secondary system's data integrity can be altered by injected formulas. SA:N – no availability impact on the secondary system.
Weakness rationale
- CWE-147 The patch directly addresses the case where user-controlled text is written into a CSV file without neutralising spreadsheet formula triggers (=, +, -, @, fullwidth variants, control characters). This is the exact definition of CWE-147.
- CWE-116 More broadly, the CSV output encoding did not escape or neutralise special characters that carry meaning in the downstream consumer (spreadsheet application), fitting the general CWE-116 category.
Attack pattern rationale
- CAPEC-117 The patch neutralises spreadsheet formula injection via CSV export, which is the canonical CSV Injection attack pattern. An attacker stores formula-like text in application fields; when the CSV is opened in a spreadsheet, the formula executes. CAPEC-117 is the most specific and directly applicable pattern. Confidence is high because the commit message, code changes, and documentation all explicitly reference spreadsheet formula neutralisation in CSV output.
Assumptions to verify
- The affected version range is not explicitly stated in the patch; the metadata field 'affected_version' contains the placeholder value '0'. All versions prior to commit adef89f5 are assumed affected.
- PR:L assumes the attacker needs at least editor-level access to create or modify case/task fields, based on the editor_required decorator visible in the surrounding code. If the application allows unauthenticated case creation, PR would be N.
- The CVSS secondary-scope impact (SC:L, SI:L) assumes the victim's spreadsheet application executes injected formulas; actual impact depends on the specific application and its security settings.
- CAPEC-117 (CSV Injection) is selected as the closest match; if this CAPEC ID is not present in the target CAPEC version, CAPEC-66 (Leverage Executable Code) would be the next-best alternative.
- The fullwidth Unicode formula triggers (=, +, -, @) are included in the fix, suggesting the developers considered non-ASCII bypass vectors; the CVSS does not separately account for this as it does not change the base score.
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 |
8 | 11 | high | 5 |
- 2026-11-06 09:54 UTC Fix developed Corrective change authored (adef89f5c82729da7bdf1c25b32ba8660b8376d5): fix: [security] Neutralise formulas in case and task CSV https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch
- 2026-11-18 14:21 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133178",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:46:27.278959Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:46:40.447Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/tools/tools.py (_cases_to_csv)",
"app/utils/csv_utils.py (new)"
],
"product": "flowintel",
"programFiles": [
"app/tools/tools.py",
"app/utils/csv_utils.py"
],
"repo": "https://github.com/flowintel/flowintel",
"vendor": "flowintel",
"versions": [
{
"lessThanOrEqual": "4.0.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"descriptions": [
{
"lang": "en",
"value": "flowintel allows users with editor-level access to author case and task fields, including aggregated tags. When these records are exported as CSV, the field values are written verbatim into the output file.\n\nBecause no sanitisation is applied to user-supplied text before CSV serialisation, an attacker can store values that begin with spreadsheet formula triggers (such as =, +, -, @, or their fullwidth Unicode equivalents, or leading control/whitespace characters). When a victim opens the exported CSV in a spreadsheet application (e.g. Microsoft Excel, LibreOffice Calc), the stored text is interpreted and executed as a live formula rather than displayed as literal text.\n\nThis can lead to unintended data manipulation within the spreadsheet, potential data exfiltration via formula functions, or execution of downstream commands depending on the spreadsheet application and its configuration.\n\nThe vulnerability requires the victim to actively open the CSV file in a spreadsheet application; the flowintel application itself is not directly compromised.\n\nAffected: \u003c4.1.0"
}
],
"impacts": [
{
"capecId": "CAPEC-117",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-117 CSV Injection"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "LOW",
"subIntegrityImpact": "LOW",
"userInteraction": "ACTIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T14:21:36Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-147",
"description": "CWE-147 Improper Neutralization of Input with Special Element Used for a Spreadsheet (CSV and DSL)",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-116",
"description": "CWE-116 Improper Encoding or Escaping of Output",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:11:56.276Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5"
}
],
"solutions": [
{
"lang": "en",
"value": "A shared CSV cell formatter (csv_safe_cell) is introduced that detects formula-like strings\u2014those beginning with =, +, -, @, their fullwidth Unicode variants, or leading control/whitespace characters\u2014and prefixes them with an apostrophe so spreadsheet applications treat the content as literal text. All case and task CSV export rows now pass every cell value through this formatter before writing, while numeric and ordinary text values are left unchanged."
}
],
"title": "CSV Formula Injection in Case and Task Exports in flowintel",
"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 version range is not explicitly stated in the patch; the metadata field \u0027affected_version\u0027 contains the placeholder value \u00270\u0027. All versions prior to commit adef89f5 are assumed affected.",
"PR:L assumes the attacker needs at least editor-level access to create or modify case/task fields, based on the editor_required decorator visible in the surrounding code. If the application allows unauthenticated case creation, PR would be N.",
"The CVSS secondary-scope impact (SC:L, SI:L) assumes the victim\u0027s spreadsheet application executes injected formulas; actual impact depends on the specific application and its security settings.",
"CAPEC-117 (CSV Injection) is selected as the closest match; if this CAPEC ID is not present in the target CAPEC version, CAPEC-66 (Leverage Executable Code) would be the next-best alternative.",
"The fullwidth Unicode formula triggers (\uff1d, \uff0b, \uff0d, \uff20) are included in the fix, suggesting the developers considered non-ASCII bypass vectors; the CVSS does not separately account for this as it does not change the base score."
],
"capecRationale": [
{
"capecId": "CAPEC-117",
"rationale": "The patch neutralises spreadsheet formula injection via CSV export, which is the canonical CSV Injection attack pattern. An attacker stores formula-like text in application fields; when the CSV is opened in a spreadsheet, the formula executes. CAPEC-117 is the most specific and directly applicable pattern. Confidence is high because the commit message, code changes, and documentation all explicitly reference spreadsheet formula neutralisation in CSV output."
}
],
"commit": "adef89f5c82729da7bdf1c25b32ba8660b8376d5",
"confidence": "high",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:N \u2013 exploitation occurs over the network via the web interface. AC:L \u2013 crafting formula-like text requires no special conditions. AT:N \u2013 no specific attack prerequisites. PR:L \u2013 the attacker needs editor-level access to create or modify case/task fields. UI:A \u2013 the victim must actively open the CSV in a spreadsheet application for the formula to execute. VC/VI/VA:N \u2013 the primary system (flowintel) suffers no direct confidentiality, integrity, or availability impact. SC:L \u2013 the secondary system (spreadsheet) may leak data via formula functions. SI:L \u2013 the secondary system\u0027s data integrity can be altered by injected formulas. SA:N \u2013 no availability impact on the secondary system.",
"fixSummary": "A shared CSV cell formatter (csv_safe_cell) is introduced that detects formula-like strings\u2014those beginning with =, +, -, @, their fullwidth Unicode variants, or leading control/whitespace characters\u2014and prefixes them with an apostrophe so spreadsheet applications treat the content as literal text. All case and task CSV export rows now pass every cell value through this formatter before writing, while numeric and ordinary text values are left unchanged.",
"generatedAt": "2026-11-18T14:21:36.786654Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 5,
"confidence": "high",
"model": "qwen3.8:27b",
"score": 8
}
],
"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": "5c27997cbe9fc0f551792f71c7bdae7d1eeaa6b849afcc78c0a6cf8af12dcf06",
"patchSummary": "New file app/utils/csv_utils.py defines csv_safe_cell(value) which returns an empty string for None, prepends an apostrophe to strings that start with tab/CR/LF or whose lstrip()-ed form begins with =, +, -, @, or fullwidth equivalents (\uff1d, \uff0b, \uff0d, \uff20), and otherwise returns the value unchanged. In app/tools/tools.py the _cases_to_csv function is modified so that both case rows and task rows are wrapped with a dict comprehension applying csv_safe_cell to every field before writer.writerow. The user manual (doc/user-manual.md) gains a note explaining the apostrophe-prefixing behaviour and that JSON exports preserve original text.",
"patchTruncated": false,
"patches": [
{
"commit": "adef89f5c82729da7bdf1c25b32ba8660b8376d5",
"date": "Fri, 6 Nov 2026 10:54:23 +0100",
"patchSha256": "5c27997cbe9fc0f551792f71c7bdae7d1eeaa6b849afcc78c0a6cf8af12dcf06",
"retrievedAt": "2026-11-18T14:21:08.763444Z",
"source": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch",
"subject": "fix: [security] Neutralise formulas in case and task CSV"
}
],
"source": "https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T14:21:36Z",
"version": "2.0.3"
},
"subject": "fix: [security] Neutralise formulas in case and task CSV",
"weaknessRationale": [
{
"cweId": "CWE-147",
"rationale": "The patch directly addresses the case where user-controlled text is written into a CSV file without neutralising spreadsheet formula triggers (=, +, -, @, fullwidth variants, control characters). This is the exact definition of CWE-147."
},
{
"cweId": "CWE-116",
"rationale": "More broadly, the CSV output encoding did not escape or neutralise special characters that carry meaning in the downstream consumer (spreadsheet application), fitting the general CWE-116 category."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (adef89f5c82729da7bdf1c25b32ba8660b8376d5): fix: [security] Neutralise formulas in case and task CSV",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch"
],
"timestamp": "2026-11-06T09:54:23Z",
"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/flowintel/flowintel/commit/adef89f5c82729da7bdf1c25b32ba8660b8376d5.patch"
],
"timestamp": "2026-11-18T14:21:08.763444Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20316"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133178",
"datePublished": "2026-11-19T14:11:56.276Z",
"dateReserved": "2026-11-19T14:11:54.087Z",
"dateUpdated": "2026-11-19T14:46:40.447Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133177 (GCVE-0-2026-133177)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:11 – Updated: 2026-11-19 14:47| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/28120b549 | 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-19 14:09 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/28120b549.patch
d09428c54d1d… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
28120b549f6b
|
fix: [security] Regular sync, pulls and feeds no longer edit | d09428c54d1d… |
Fix summary
The fix introduces a privilege gate on organisation detail updates during sharing group capture. A new static context flag (captureRemote) is set by Feed and Server pull code paths to indicate whether the capture originates from an internal link. A new authorization check (__mayUpdateOrgDetails) permits overwriting organisation fields only when the operation is an internal sync or the acting user holds perm_site_admin or perm_sync_internal. All other sync, pull, and feed operations are restricted to matching or creating organisations without editing their existing details.
Patch summary
In SharingGroup.php, a static $remoteCapture flag and captureRemote() wrapper are added; captureSG() now computes an $updateOrgDetails boolean via __mayUpdateOrgDetails() and passes it to captureSGOrgs(), which forwards it to Organisation::captureOrg() instead of the previous $force parameter. Feed.php wraps both downloadAndSaveEventFromFeed() and downloadFromFeedInitiator() in SharingGroup::captureRemote(false, ...). Server.php refactors pull() to detect the internal flag from the server record and wraps the actual pull in SharingGroup::captureRemote($internal, ...). A regression test class (OrganisationDetailsSyncScope) in tests/testregressions.py verifies that a plain sync user cannot modify org details, while an internal-sync user and a site admin can.
CVSS rationale
AV:N: MISP is a network-accessible web application; sync, pull, and feed operations occur over HTTP. AC:L: exploitation requires only pushing a sharing group with a newer modified date and a roster containing modified organisation details; no race conditions or special timing are needed. AT:N: no attack-target manipulation is required. PR:L: the attacker needs a low-privileged sync user account (perm_sync) or control of an external feed/pull source; no admin credentials are required. UI:N: no user interaction is needed; the overwrite occurs automatically during capture. VC:N: no confidential data is disclosed. VI:L: organisation metadata (type, nationality, sector, contacts) can be silently altered, a limited integrity impact. VA:N: no availability impact. SC/SI/SA:N: the impact is confined to the MISP instance's own organisation records with no cross-scope effect.
Weakness rationale
- CWE-862 The sharing group capture path performed organisation detail updates without checking whether the acting user or data source was authorized to modify those fields. Any sync user, external feed, or non-internal pull could overwrite organisation records, indicating a missing authorization check on the write operation.
- CWE-285 The authorization model did not distinguish between creating/matching an organisation and editing its details during sync, pull, or feed operations. The privilege boundary between regular sync users and internal-sync/site-admin users was not enforced for organisation field updates.
Attack pattern rationale
- CAPEC-114 The application incorrectly adjusted the effective privilege level during sync, pull, and feed operations: external data sources and low-privileged sync users were granted the ability to modify organisation records that should have been restricted to site admins or internal-sync users. The attacker exploits this over-privileged code path by pushing a sharing group roster containing modified organisation details. CAPEC-114 is the closest match because the core issue is that the application's privilege model did not correctly scope what operations a given role or data source may perform on organisation records. Uncertainty: no CAPEC pattern specifically describes data-integrity abuse via a sync/replication channel, so CAPEC-114 is selected as the best available approximation.
Assumptions to verify
- The affected MISP version range is not specified in the patch; the fix is applied to the main development branch and the exact version boundary is unknown.
- PR:L assumes the attacker holds a sync user account (perm_sync) or controls an external feed/pull source; if the attacker must first compromise a feed, the effective privilege requirement could be higher.
- VI:L assumes that overwriting organisation metadata (type, nationality, sector, contacts) constitutes a limited integrity impact; if downstream consumers rely on these fields for access decisions, the impact could be higher.
- CAPEC-114 is selected as the closest available pattern; no CAPEC specifically models data-integrity abuse through a replication/sync channel, so the mapping is approximate.
- The Co-Authored-By line credits Claude Opus 5.5 as a remediation developer; this is recorded as it appears in the commit metadata but the role is inferred from the co-authorship context.
- AT:N assumes no special conditions on the target are needed beyond a standard MISP deployment with sync, pull, or feed functionality enabled.
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-12 08:26 UTC Fix developed Corrective change authored (28120b549f6b3949d7354731cd483cc1e436cf8c): fix: [security] Regular sync, pulls and feeds no longer edit https://github.com/MISP/MISP/commit/28120b549.patch
- 2026-11-19 14:08 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/28120b549.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133177",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:47:40.774810Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:47:51.499Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"app/Model/SharingGroup.php",
"app/Model/Feed.php",
"app/Model/Server.php"
],
"product": "MISP",
"programFiles": [
"app/Model/SharingGroup.php",
"app/Model/Feed.php",
"app/Model/Server.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"
},
{
"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 sharing group capture logic. When a sharing group is re-captured with a newer modified timestamp and an updated roster, the application unconditionally overwrote the type, nationality, sector, and contacts fields of every organisation listed in the roster, including the host organisation. This behaviour was reachable by any user holding the perm_sync role, and additionally by any external server pulled from or any feed fetched, because those operations execute with the privileges of the site administrator who initiated them. As a result, a low-privileged sync user or a malicious/compromised external feed or pull source could silently corrupt organisation records on the receiving MISP instance without any site-admin or internal-sync authorization. The vulnerability does not disclose data or affect availability; the impact is limited to integrity of organisation metadata (type, nationality, sector, contacts). The fix restricts organisation detail updates to internal sync operations (pulls over links flagged as internal, or senders holding perm_sync_internal) and site administrators; all other sync, pull, and feed operations may only match existing organisations by UUID or create new ones, without modifying their stored details."
}
],
"impacts": [
{
"capecId": "CAPEC-114",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-114 Exploiting Incorrectly Adjusted Privileges"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW",
"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-19T14:09: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-285",
"description": "CWE-285 Improper Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:11:36.093Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/28120b549"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix introduces a privilege gate on organisation detail updates during sharing group capture. A new static context flag (captureRemote) is set by Feed and Server pull code paths to indicate whether the capture originates from an internal link. A new authorization check (__mayUpdateOrgDetails) permits overwriting organisation fields only when the operation is an internal sync or the acting user holds perm_site_admin or perm_sync_internal. All other sync, pull, and feed operations are restricted to matching or creating organisations without editing their existing details."
}
],
"title": "MISP: Insufficient Authorization Allows Sync Users and External Feeds to Overwrite Organisation Details",
"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 fix is applied to the main development branch and the exact version boundary is unknown.",
"PR:L assumes the attacker holds a sync user account (perm_sync) or controls an external feed/pull source; if the attacker must first compromise a feed, the effective privilege requirement could be higher.",
"VI:L assumes that overwriting organisation metadata (type, nationality, sector, contacts) constitutes a limited integrity impact; if downstream consumers rely on these fields for access decisions, the impact could be higher.",
"CAPEC-114 is selected as the closest available pattern; no CAPEC specifically models data-integrity abuse through a replication/sync channel, so the mapping is approximate.",
"The Co-Authored-By line credits Claude Opus 5.5 as a remediation developer; this is recorded as it appears in the commit metadata but the role is inferred from the co-authorship context.",
"AT:N assumes no special conditions on the target are needed beyond a standard MISP deployment with sync, pull, or feed functionality enabled."
],
"capecRationale": [
{
"capecId": "CAPEC-114",
"rationale": "The application incorrectly adjusted the effective privilege level during sync, pull, and feed operations: external data sources and low-privileged sync users were granted the ability to modify organisation records that should have been restricted to site admins or internal-sync users. The attacker exploits this over-privileged code path by pushing a sharing group roster containing modified organisation details. CAPEC-114 is the closest match because the core issue is that the application\u0027s privilege model did not correctly scope what operations a given role or data source may perform on organisation records. Uncertainty: no CAPEC pattern specifically describes data-integrity abuse via a sync/replication channel, so CAPEC-114 is selected as the best available approximation."
}
],
"commit": "28120b549f6b3949d7354731cd483cc1e436cf8c",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
}
],
"cvssRationale": "AV:N: MISP is a network-accessible web application; sync, pull, and feed operations occur over HTTP. AC:L: exploitation requires only pushing a sharing group with a newer modified date and a roster containing modified organisation details; no race conditions or special timing are needed. AT:N: no attack-target manipulation is required. PR:L: the attacker needs a low-privileged sync user account (perm_sync) or control of an external feed/pull source; no admin credentials are required. UI:N: no user interaction is needed; the overwrite occurs automatically during capture. VC:N: no confidential data is disclosed. VI:L: organisation metadata (type, nationality, sector, contacts) can be silently altered, a limited integrity impact. VA:N: no availability impact. SC/SI/SA:N: the impact is confined to the MISP instance\u0027s own organisation records with no cross-scope effect.",
"draft": false,
"fixSummary": "The fix introduces a privilege gate on organisation detail updates during sharing group capture. A new static context flag (captureRemote) is set by Feed and Server pull code paths to indicate whether the capture originates from an internal link. A new authorization check (__mayUpdateOrgDetails) permits overwriting organisation fields only when the operation is an internal sync or the acting user holds perm_site_admin or perm_sync_internal. All other sync, pull, and feed operations are restricted to matching or creating organisations without editing their existing details.",
"generatedAt": "2026-11-19T14:09:16.804907Z",
"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": "d09428c54d1d346e930e8bbf886cda9a96e024ec1011f70637284aae96a11a6f",
"patchSummary": "In SharingGroup.php, a static $remoteCapture flag and captureRemote() wrapper are added; captureSG() now computes an $updateOrgDetails boolean via __mayUpdateOrgDetails() and passes it to captureSGOrgs(), which forwards it to Organisation::captureOrg() instead of the previous $force parameter. Feed.php wraps both downloadAndSaveEventFromFeed() and downloadFromFeedInitiator() in SharingGroup::captureRemote(false, ...). Server.php refactors pull() to detect the internal flag from the server record and wraps the actual pull in SharingGroup::captureRemote($internal, ...). A regression test class (OrganisationDetailsSyncScope) in tests/testregressions.py verifies that a plain sync user cannot modify org details, while an internal-sync user and a site admin can.",
"patchTruncated": false,
"patches": [
{
"commit": "28120b549f6b3949d7354731cd483cc1e436cf8c",
"date": "Thu, 12 Nov 2026 09:26:34 +0100",
"patchSha256": "d09428c54d1d346e930e8bbf886cda9a96e024ec1011f70637284aae96a11a6f",
"retrievedAt": "2026-11-19T14:08:29.143191Z",
"source": "https://github.com/MISP/MISP/commit/28120b549.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/28120b549.patch",
"subject": "fix: [security] Regular sync, pulls and feeds no longer edit"
}
],
"source": "https://github.com/MISP/MISP/commit/28120b549.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:09:16Z",
"version": "2.0.3"
},
"subject": "fix: [security] Regular sync, pulls and feeds no longer edit",
"weaknessRationale": [
{
"cweId": "CWE-862",
"rationale": "The sharing group capture path performed organisation detail updates without checking whether the acting user or data source was authorized to modify those fields. Any sync user, external feed, or non-internal pull could overwrite organisation records, indicating a missing authorization check on the write operation."
},
{
"cweId": "CWE-285",
"rationale": "The authorization model did not distinguish between creating/matching an organisation and editing its details during sync, pull, or feed operations. The privilege boundary between regular sync users and internal-sync/site-admin users was not enforced for organisation field updates."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (28120b549f6b3949d7354731cd483cc1e436cf8c): fix: [security] Regular sync, pulls and feeds no longer edit",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/28120b549.patch"
],
"timestamp": "2026-11-12T08:26:34Z",
"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/28120b549.patch"
],
"timestamp": "2026-11-19T14:08:29.143191Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20326"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133177",
"datePublished": "2026-11-19T14:11:36.093Z",
"dateReserved": "2026-11-19T14:11:33.323Z",
"dateUpdated": "2026-11-19T14:47:51.499Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133175 (GCVE-0-2026-133175)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:06 – Updated: 2026-11-19 14:48| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/19a5e8444 | 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-19 14:02 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/19a5e8444.patch
f2ec162442da… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
19a5e8444ff2
|
fix: [security] Synced proposals reach only events the sender | f2ec162442da… |
Fix summary
The fix enforces proper authorization scoping at two levels. First, pushProposals now resolves the event through fetchSimpleEvent (which applies ACL) and the pull path uses a new __eventSyncedWithServer helper that verifies the event is actually shared with the syncing server before accepting proposals. The stored event_id, event_uuid, and event_org_id are taken from the local event record, not from sender-supplied fields. Second, a new findTargetAttribute method requires all three of Attribute.id, Attribute.event_id, and Attribute.uuid to match simultaneously, ensuring an edit proposal can only affect an attribute within its own event. Acceptance paths now reject the proposal if the target attribute cannot be resolved within the correct event scope.
Patch summary
In EventsController::pushProposals, the raw Event::find by UUID was replaced with Event::fetchSimpleEvent (ACL-aware) and the inline proposal-saving loop was extracted into ShadowAttribute::capture which now receives the already-authorized event and overwrites event_id, event_uuid, and event_org_id from the local record. In ShadowAttributesController::__accept and ShadowAttribute::acceptProposal, the unscoped Attribute::find by UUID was replaced with ShadowAttribute::findTargetAttribute which matches id + event_id + uuid. A new private method __eventSyncedWithServer validates that a pulled proposal's event is shared with the remote server (via distribution level, sharing group, or orgc ownership) before capture. pullProposals now pre-resolves and caches the authorized event per UUID. Regression tests (ProposalSyncScope) verify hidden events return the same response as missing events, stored columns reflect local identity, cross-event edit proposals are rejected, and duplicate/newer-version handling is correct
CVSS rationale
AV:N - MISP is a network-accessible web application. AC:L - the attack requires crafting a standard API request with a known/guessed UUID; no race conditions or special timing needed. AT:N - no prior data tampering required; the attack payload is the request itself. PR:L - requires an authenticated user with perm_sync. UI:N - no victim interaction needed. VC:L - the sync user can retrieve event data (including attributes) from events they should not see. VI:H - the user can modify or delete attributes in events outside their authorization scope, and inject proposals onto restricted events. VA:N - no denial-of-service impact evidenced. SC/SI/SA:N - impact is confined to the vulnerable MISP instance's own data; no cross-system impact is demonstrated by the patch.
Weakness rationale
- CWE-862 The pushProposals endpoint and the pullProposals capture path did not verify that the sync user had access to the target event before storing proposals. The event was located by a user-supplied UUID with no ACL enforcement, allowing proposals to be attached to events outside the user's permitted scope.
- CWE-639 The edit-proposal acceptance path resolved the target attribute using only the user-controlled UUID field (Attribute.uuid) without scoping to the event, allowing an attacker to reference an attribute in a different event and have it modified or deleted. The user-controlled key (uuid) was used as the sole discriminator for a sensitive operation.
Attack pattern rationale
- CAPEC-126 The sync user holds legitimate perm_sync privileges, but the application fails to correctly scope those privileges to the events and attributes the user is authorized to access. The attacker exploits the missing authorization boundary to perform actions (push proposals to restricted events, modify foreign attributes) that exceed the intended scope of their role. This is the closest CAPEC to the observed pattern of an authenticated user leveraging an authorization gap to reach resources outside their permitted set. Uncertainty: CAPEC-126 typically describes privilege escalation; here the user already has sync rights but the application's scoping is incorrect, making this a best-available match rather than an exact fit.
Assumptions to verify
- The affected MISP version range is not specified in the patch; the fix is applied to the main development branch and the exact version boundary is unknown.
- CVSS PR:L assumes the attacker needs only a standard sync-permission role; if the deployment requires additional administrative setup to enable sync, the effective privilege requirement may be higher.
- CVSS VC:L assumes the attacker can observe event data in the API response; if the deployment suppresses event details in error responses, confidentiality impact may be lower.
- CAPEC-126 is the closest available mapping; the exact pattern is an authorization-scoping gap rather than a classic privilege escalation, so the mapping is approximate.
- The SSVC technical_impact of 'total' assumes the attacker can fully modify or delete target attributes; if the deployment has additional compensating controls (e.g., audit logging, backup restoration), the effective impact may be partial.
- The patch does not specify whether the vulnerability is exploitable only during active server-to-server sync or also via direct API calls to pushProposals; both paths are fixed, suggesting both were vulnerable.
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 16:40 UTC Fix developed Corrective change authored (19a5e8444ff21a8304c5ac3bdd91f5dae9599472): fix: [security] Synced proposals reach only events the sender https://github.com/MISP/MISP/commit/19a5e8444.patch
- 2026-11-19 14:02 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/19a5e8444.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133175",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:48:50.913251Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:48:59.217Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"EventsController (pushProposals)",
"ShadowAttributesController (__accept)",
"ShadowAttribute model (capture, pullProposals, acceptProposal)"
],
"product": "misp",
"programFiles": [
"app/Controller/EventsController.php",
"app/Controller/ShadowAttributesController.php",
"app/Model/ShadowAttribute.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"
}
],
"descriptions": [
{
"lang": "en",
"value": "MISP contains an authorization bypass in its server-to-server proposal synchronization mechanism. Two related flaws were identified:\n\n1. The events/pushProposals endpoint located the target event by UUID without enforcing any access-control check. A sync user with perm_sync could push shadow-attribute proposals to any event on the local instance, including events with restricted distribution (e.g., distribution level 0, visible only to the owning organisation). The stored proposal also carried the sender-supplied event_uuid and event_org_id rather than the local event\u0027s actual identity, corrupting the data model.\n\n2. When accepting an edit proposal (old_id != 0), the code resolved the target live attribute by UUID alone (Attribute.uuid = shadow.uuid) without scoping the lookup to the proposal\u0027s own event. A malicious sync user could therefore craft a proposal whose uuid matched an attribute in a different event; upon acceptance, the wrong attribute would be modified or deleted. The same unscoped lookup existed in the ShadowAttribute::acceptProposal path.\n\nPreconditions: an authenticated user with sync permission (perm_sync) on a MISP instance that participates in server-to-server synchronisation. The attacker must know or enumerate the UUID of a target event or attribute.\n\nSecurity impact: unauthorised read access to restricted events, unauthorised insertion of proposals onto events the user cannot see, and unauthorised modification or deletion of attributes belonging to other events. This compromises the confidentiality and integrity of threat-intelligence data across organisational boundaries within a MISP deployment."
}
],
"impacts": [
{
"capecId": "CAPEC-126",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-126 Exploiting Incorrectly Adjusted Privileges"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 6.9,
"baseSeverity": "MEDIUM",
"privilegesRequired": "HIGH",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/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-19T14:02:59Z",
"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-19T14:06:40.349Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/19a5e8444"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix enforces proper authorization scoping at two levels. First, pushProposals now resolves the event through fetchSimpleEvent (which applies ACL) and the pull path uses a new __eventSyncedWithServer helper that verifies the event is actually shared with the syncing server before accepting proposals. The stored event_id, event_uuid, and event_org_id are taken from the local event record, not from sender-supplied fields. Second, a new findTargetAttribute method requires all three of Attribute.id, Attribute.event_id, and Attribute.uuid to match simultaneously, ensuring an edit proposal can only affect an attribute within its own event. Acceptance paths now reject the proposal if the target attribute cannot be resolved within the correct event scope."
}
],
"title": "MISP Missing Authorization in Sync Proposal Endpoints Allows Cross-Event Data Access and Modification",
"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 fix is applied to the main development branch and the exact version boundary is unknown.",
"CVSS PR:L assumes the attacker needs only a standard sync-permission role; if the deployment requires additional administrative setup to enable sync, the effective privilege requirement may be higher.",
"CVSS VC:L assumes the attacker can observe event data in the API response; if the deployment suppresses event details in error responses, confidentiality impact may be lower.",
"CAPEC-126 is the closest available mapping; the exact pattern is an authorization-scoping gap rather than a classic privilege escalation, so the mapping is approximate.",
"The SSVC technical_impact of \u0027total\u0027 assumes the attacker can fully modify or delete target attributes; if the deployment has additional compensating controls (e.g., audit logging, backup restoration), the effective impact may be partial.",
"The patch does not specify whether the vulnerability is exploitable only during active server-to-server sync or also via direct API calls to pushProposals; both paths are fixed, suggesting both were vulnerable."
],
"capecRationale": [
{
"capecId": "CAPEC-126",
"rationale": "The sync user holds legitimate perm_sync privileges, but the application fails to correctly scope those privileges to the events and attributes the user is authorized to access. The attacker exploits the missing authorization boundary to perform actions (push proposals to restricted events, modify foreign attributes) that exceed the intended scope of their role. This is the closest CAPEC to the observed pattern of an authenticated user leveraging an authorization gap to reach resources outside their permitted set. Uncertainty: CAPEC-126 typically describes privilege escalation; here the user already has sync rights but the application\u0027s scoping is incorrect, making this a best-available match rather than an exact fit."
}
],
"commit": "19a5e8444ff21a8304c5ac3bdd91f5dae9599472",
"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"
}
],
"cvssRationale": "AV:N - MISP is a network-accessible web application. AC:L - the attack requires crafting a standard API request with a known/guessed UUID; no race conditions or special timing needed. AT:N - no prior data tampering required; the attack payload is the request itself. PR:L - requires an authenticated user with perm_sync. UI:N - no victim interaction needed. VC:L - the sync user can retrieve event data (including attributes) from events they should not see. VI:H - the user can modify or delete attributes in events outside their authorization scope, and inject proposals onto restricted events. VA:N - no denial-of-service impact evidenced. SC/SI/SA:N - impact is confined to the vulnerable MISP instance\u0027s own data; no cross-system impact is demonstrated by the patch.",
"draft": false,
"fixSummary": "The fix enforces proper authorization scoping at two levels. First, pushProposals now resolves the event through fetchSimpleEvent (which applies ACL) and the pull path uses a new __eventSyncedWithServer helper that verifies the event is actually shared with the syncing server before accepting proposals. The stored event_id, event_uuid, and event_org_id are taken from the local event record, not from sender-supplied fields. Second, a new findTargetAttribute method requires all three of Attribute.id, Attribute.event_id, and Attribute.uuid to match simultaneously, ensuring an edit proposal can only affect an attribute within its own event. Acceptance paths now reject the proposal if the target attribute cannot be resolved within the correct event scope.",
"generatedAt": "2026-11-19T14:02:59.946447Z",
"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": "f2ec162442da92be164bb57d7bd5cd1ddffdf1febdf6b1305bfaa0b7a182ffc3",
"patchSummary": "In EventsController::pushProposals, the raw Event::find by UUID was replaced with Event::fetchSimpleEvent (ACL-aware) and the inline proposal-saving loop was extracted into ShadowAttribute::capture which now receives the already-authorized event and overwrites event_id, event_uuid, and event_org_id from the local record. In ShadowAttributesController::__accept and ShadowAttribute::acceptProposal, the unscoped Attribute::find by UUID was replaced with ShadowAttribute::findTargetAttribute which matches id + event_id + uuid. A new private method __eventSyncedWithServer validates that a pulled proposal\u0027s event is shared with the remote server (via distribution level, sharing group, or orgc ownership) before capture. pullProposals now pre-resolves and caches the authorized event per UUID. Regression tests (ProposalSyncScope) verify hidden events return the same response as missing events, stored columns reflect local identity, cross-event edit proposals are rejected, and duplicate/newer-version handling is correct",
"patchTruncated": false,
"patches": [
{
"commit": "19a5e8444ff21a8304c5ac3bdd91f5dae9599472",
"date": "Wed, 11 Nov 2026 17:40:47 +0100",
"patchSha256": "f2ec162442da92be164bb57d7bd5cd1ddffdf1febdf6b1305bfaa0b7a182ffc3",
"retrievedAt": "2026-11-19T14:02:15.217844Z",
"source": "https://github.com/MISP/MISP/commit/19a5e8444.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/19a5e8444.patch",
"subject": "fix: [security] Synced proposals reach only events the sender"
}
],
"source": "https://github.com/MISP/MISP/commit/19a5e8444.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:02:59Z",
"version": "2.0.3"
},
"subject": "fix: [security] Synced proposals reach only events the sender",
"weaknessRationale": [
{
"cweId": "CWE-862",
"rationale": "The pushProposals endpoint and the pullProposals capture path did not verify that the sync user had access to the target event before storing proposals. The event was located by a user-supplied UUID with no ACL enforcement, allowing proposals to be attached to events outside the user\u0027s permitted scope."
},
{
"cweId": "CWE-639",
"rationale": "The edit-proposal acceptance path resolved the target attribute using only the user-controlled UUID field (Attribute.uuid) without scoping to the event, allowing an attacker to reference an attribute in a different event and have it modified or deleted. The user-controlled key (uuid) was used as the sole discriminator for a sensitive operation."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (19a5e8444ff21a8304c5ac3bdd91f5dae9599472): fix: [security] Synced proposals reach only events the sender",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/19a5e8444.patch"
],
"timestamp": "2026-11-11T16:40:47Z",
"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/19a5e8444.patch"
],
"timestamp": "2026-11-19T14:02:15.217844Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20319"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133175",
"datePublished": "2026-11-19T14:06:40.349Z",
"dateReserved": "2026-11-19T14:06:35.301Z",
"dateUpdated": "2026-11-19T14:48:59.217Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133165 (GCVE-0-2026-133165)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:00 – Updated: 2026-11-19 14:20| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/c9bd0eff5 | 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-19 13:57 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/c9bd0eff5.patch
e307b313d1d2… - Confidence
- high
| Commit | Subject | Patch SHA-256 |
|---|---|---|
c9bd0eff523b
|
fix: [security] Event saves no longer rewrite other events' | e307b313d1d2… |
Fix summary
The fix adds an event-scope ownership check in ObjectReference::captureReference(). After locating an existing reference by UUID, the code now verifies that the reference's event_id matches the event currently being saved. If the UUID belongs to a different event, the reference is skipped (neither updated nor recreated in the saving event) and a warning-level system log entry is written recording the blocked operation, the target event ID, and the foreign event ID that owns the UUID.
Patch summary
In app/Model/ObjectReference.php, a nine-line guard is inserted in captureReference() immediately after the existing-reference lookup: it casts both the stored event_id and the incoming $eventId to integers and compares them; on mismatch it calls loadLog()->createLogEntry() with a 'warning' severity and a descriptive message, then returns true to skip the update. In tests/testregressions.py, a new ObjectReferenceCaptureScope test class (156 lines) is added with four test methods: (1) event add with a forged foreign UUID leaves the victim reference unchanged and does not create a copy; (2) event edit with a forged foreign UUID leaves the victim reference unchanged; (3) the owner can still update their own reference's comment and timestamp; (4) a genuinely new reference UUID is still created normally. The tests use two separate organizations and least-privileged users to verify cross-tenant isolation.
CVSS rationale
AV:N: MISP is a network-accessible web application with a REST API. AC:L: the attacker only needs to include a known or discovered UUID in a standard event save payload; no race conditions or special timing required. AT:N: no need to intercept or tamper with in-transit data. PR:L: requires an authenticated user with permission to add or edit events (least-privileged role suffices per the regression tests). UI:N: no victim interaction needed. VC:N: the attack writes to records; no confidentiality impact is demonstrated. VI:H: multiple fields (relationship_type, comment, deleted, timestamp) on foreign references can be overwritten, corrupting data integrity. VA:N: setting the deleted flag is a data modification, not a service denial. SC:N: no impact on external systems' confidentiality. SI:H: integrity of data belonging to other organizations within the same MISP instance is compromised. SA:N: no security-functionality impact on other components.
Weakness rationale
- CWE-639 The object reference UUID is a user-supplied key used to look up and modify a record. The lookup was performed without verifying that the record belongs to the event (and by extension the organization) of the authenticated user, allowing modification of records outside the user's authorization scope.
- CWE-640 The reference UUID was resolved against the entire instance's object references table rather than being constrained to the event being saved, resulting in resolution to an unintended record in a different event/organization.
Attack pattern rationale
- CAPEC-114 The attacker manipulates the UUID parameter within a legitimate event save request to target a different object reference record. The application trusts the UUID as a direct pointer without validating ownership scope. CAPEC-114 is the closest match because the core technique is supplying a crafted identifier parameter to redirect a write operation to an unintended resource. Uncertainty: no dedicated CAPEC exists for cross-tenant IDOR via UUID; CAPEC-114 is the best available approximation.
Assumptions to verify
- The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.
- PR:L assumes the attacker needs only a standard authenticated user with event add/edit permission; the regression tests confirm a least-privileged role suffices.
- The CAPEC-114 mapping is an approximation; no CAPEC specifically covers cross-tenant IDOR via UUID in a multi-tenant application.
- VC:N assumes the attack does not enable reading foreign reference data; the patch evidence shows only write/overwrite impact.
- VA:N assumes setting the 'deleted' flag on a reference is an integrity modification rather than an availability denial; the reference record still exists in the database.
- The commit date of 2026-11-11 is taken at face value from the patch metadata.
- No evidence of active exploitation or public PoC was found in the patch or metadata; SSVC exploitation is set to 'none'.
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 | high | 7 |
- 2026-11-11 13:24 UTC Fix developed Corrective change authored (c9bd0eff523b6936b66923830c1c26fe3bee3d53): fix: [security] Event saves no longer rewrite other events' https://github.com/MISP/MISP/commit/c9bd0eff5.patch
- 2026-11-19 13:56 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/c9bd0eff5.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133165",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:19:53.649869Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:20:04.824Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"ObjectReference model (app/Model/ObjectReference.php)",
"Event add/edit (REST, sync, feeds)"
],
"product": "misp",
"programFiles": [
"app/Model/ObjectReference.php"
],
"repo": "https://github.com/MISP/MISP",
"vendor": "misp",
"versions": [
{
"lessThanOrEqual": "2.5.51",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.5.51",
"versionStartIncluding": "0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "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": "Jeroen Pinoy"
},
{
"lang": "en",
"type": "reporter",
"value": "CERT.pl"
}
],
"descriptions": [
{
"lang": "en",
"value": "MISP contains an authorization and scope flaw in the ObjectReference model\u0027s captureReference method. When a user saves an event (via REST API, sync, or feeds), any object reference included in the payload is looked up by its UUID across the entire MISP instance rather than being scoped to the event being saved. An authenticated user with permission to add or edit events can therefore include the UUID of an object reference belonging to a different event\u2014including events in other organizations that the user cannot view\u2014and cause the system to overwrite that foreign reference\u0027s relationship_type, comment, deleted flag, and timestamp with attacker-supplied values. The affected reference is neither deleted nor recreated in the attacker\u0027s event; its fields are silently rewritten in place. This constitutes a cross-tenant integrity violation: data integrity of object references in events the attacker has no read or write access to is compromised. The vulnerability is reachable through any event save path (REST add/edit, inter-instance sync, feed ingestion) and requires only a valid authenticated session with event modification privileges and knowledge or discovery of a target reference UUID."
}
],
"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": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW",
"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-19T13:57:00Z",
"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"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-640",
"description": "CWE-640 Weak Reference Resolution",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:00:54.191Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/c9bd0eff5"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix adds an event-scope ownership check in ObjectReference::captureReference(). After locating an existing reference by UUID, the code now verifies that the reference\u0027s event_id matches the event currently being saved. If the UUID belongs to a different event, the reference is skipped (neither updated nor recreated in the saving event) and a warning-level system log entry is written recording the blocked operation, the target event ID, and the foreign event ID that owns the UUID."
}
],
"title": "MISP Object Reference Cross-Event Integrity Violation via UUID Scope Bypass",
"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 are assumed affected.",
"PR:L assumes the attacker needs only a standard authenticated user with event add/edit permission; the regression tests confirm a least-privileged role suffices.",
"The CAPEC-114 mapping is an approximation; no CAPEC specifically covers cross-tenant IDOR via UUID in a multi-tenant application.",
"VC:N assumes the attack does not enable reading foreign reference data; the patch evidence shows only write/overwrite impact.",
"VA:N assumes setting the \u0027deleted\u0027 flag on a reference is an integrity modification rather than an availability denial; the reference record still exists in the database.",
"The commit date of 2026-11-11 is taken at face value from the patch metadata.",
"No evidence of active exploitation or public PoC was found in the patch or metadata; SSVC exploitation is set to \u0027none\u0027."
],
"capecRationale": [
{
"capecId": "CAPEC-114",
"rationale": "The attacker manipulates the UUID parameter within a legitimate event save request to target a different object reference record. The application trusts the UUID as a direct pointer without validating ownership scope. CAPEC-114 is the closest match because the core technique is supplying a crafted identifier parameter to redirect a write operation to an unintended resource. Uncertainty: no dedicated CAPEC exists for cross-tenant IDOR via UUID; CAPEC-114 is the best available approximation."
}
],
"commit": "c9bd0eff523b6936b66923830c1c26fe3bee3d53",
"confidence": "high",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA, Jeroen Pinoy 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": "Jeroen Pinoy"
},
{
"lang": "en",
"type": "reporter",
"value": "CERT.pl"
}
],
"cvssRationale": "AV:N: MISP is a network-accessible web application with a REST API. AC:L: the attacker only needs to include a known or discovered UUID in a standard event save payload; no race conditions or special timing required. AT:N: no need to intercept or tamper with in-transit data. PR:L: requires an authenticated user with permission to add or edit events (least-privileged role suffices per the regression tests). UI:N: no victim interaction needed. VC:N: the attack writes to records; no confidentiality impact is demonstrated. VI:H: multiple fields (relationship_type, comment, deleted, timestamp) on foreign references can be overwritten, corrupting data integrity. VA:N: setting the deleted flag is a data modification, not a service denial. SC:N: no impact on external systems\u0027 confidentiality. SI:H: integrity of data belonging to other organizations within the same MISP instance is compromised. SA:N: no security-functionality impact on other components.",
"draft": false,
"fixSummary": "The fix adds an event-scope ownership check in ObjectReference::captureReference(). After locating an existing reference by UUID, the code now verifies that the reference\u0027s event_id matches the event currently being saved. If the UUID belongs to a different event, the reference is skipped (neither updated nor recreated in the saving event) and a warning-level system log entry is written recording the blocked operation, the target event ID, and the foreign event ID that owns the UUID.",
"generatedAt": "2026-11-19T13:57:00.911027Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 7,
"confidence": "high",
"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": "e307b313d1d2d25606f7daa11657394949688c2721f729461a37761c268012e9",
"patchSummary": "In app/Model/ObjectReference.php, a nine-line guard is inserted in captureReference() immediately after the existing-reference lookup: it casts both the stored event_id and the incoming $eventId to integers and compares them; on mismatch it calls loadLog()-\u003ecreateLogEntry() with a \u0027warning\u0027 severity and a descriptive message, then returns true to skip the update. In tests/testregressions.py, a new ObjectReferenceCaptureScope test class (156 lines) is added with four test methods: (1) event add with a forged foreign UUID leaves the victim reference unchanged and does not create a copy; (2) event edit with a forged foreign UUID leaves the victim reference unchanged; (3) the owner can still update their own reference\u0027s comment and timestamp; (4) a genuinely new reference UUID is still created normally. The tests use two separate organizations and least-privileged users to verify cross-tenant isolation.",
"patchTruncated": false,
"patches": [
{
"commit": "c9bd0eff523b6936b66923830c1c26fe3bee3d53",
"date": "Wed, 11 Nov 2026 14:24:50 +0100",
"patchSha256": "e307b313d1d2d25606f7daa11657394949688c2721f729461a37761c268012e9",
"retrievedAt": "2026-11-19T13:56:17.554618Z",
"source": "https://github.com/MISP/MISP/commit/c9bd0eff5.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/c9bd0eff5.patch",
"subject": "fix: [security] Event saves no longer rewrite other events\u0027"
}
],
"source": "https://github.com/MISP/MISP/commit/c9bd0eff5.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T13:57:00Z",
"version": "2.0.3"
},
"subject": "fix: [security] Event saves no longer rewrite other events\u0027",
"weaknessRationale": [
{
"cweId": "CWE-639",
"rationale": "The object reference UUID is a user-supplied key used to look up and modify a record. The lookup was performed without verifying that the record belongs to the event (and by extension the organization) of the authenticated user, allowing modification of records outside the user\u0027s authorization scope."
},
{
"cweId": "CWE-640",
"rationale": "The reference UUID was resolved against the entire instance\u0027s object references table rather than being constrained to the event being saved, resulting in resolution to an unintended record in a different event/organization."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (c9bd0eff523b6936b66923830c1c26fe3bee3d53): fix: [security] Event saves no longer rewrite other events\u0027",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/c9bd0eff5.patch"
],
"timestamp": "2026-11-11T13:24:50Z",
"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/c9bd0eff5.patch"
],
"timestamp": "2026-11-19T13:56:17.554618Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20341"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133165",
"datePublished": "2026-11-19T14:00:54.191Z",
"dateReserved": "2026-11-19T14:00:45.542Z",
"dateUpdated": "2026-11-19T14:20:04.824Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133163 (GCVE-0-2026-133163)
Vulnerability from cvelistv5 – Published: 2026-11-19 13:55 – Updated: 2026-11-19 14:25| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/e4fa73719 | 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-19 13:50 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/e4fa73719.patch
5b0f387b75bb… - Confidence
- high
| Commit | Subject | Patch SHA-256 |
|---|---|---|
e4fa7371938d
|
fix: [security] Sync users change protected events only | 5b0f387b75bb… |
Fix summary
A shared authorization check (isProtectedFromSyncUser / assertNotProtectedFromSyncUser) was introduced in the Event model and enforced across all write paths. The check denies any non-internal, non-site-admin sync user from modifying a protected event through any route other than events/edit with a valid signature. The check is now invoked in the ACL component (modify, publish, tag), in the CryptographicKeys, Events, and Tags controllers, and in the Event, EventReport, Galaxy, and MispAttribute models, closing every previously unprotected write path.
Patch summary
Added Event::isProtectedFromSyncUser() and Event::assertNotProtectedFromSyncUser() methods that return true / throw ForbiddenException when the user has perm_sync but lacks perm_site_admin and perm_sync_internal, and the target event has protected=1. Inserted calls to these methods in: ACLComponent::canModifyEvent(), canPublishEvent(), canModifyTag(); CryptographicKeysController::add() and delete(); EventsController::populate(), upload_sample(), upload_analysis_file(); TagsController::__findObjectByUuid(); Event::userCanModifyEvent() and upload_stix(); EventReport::fetchIfAuthorized(); Galaxy::detachCluster() and detachClusterByTagId(); MispAttribute::deleteAttribute(). Also added the 'protected' field to the event query in upload_sample. Added a comprehensive regression test class (ProtectedEventSyncWrites) covering all affected routes plus control tests for internal sync users, org admins, and post-unprotect behavior.
CVSS rationale
AV:N: MISP is a network-accessible web application. AC:L: Exploitation requires only standard API calls with a valid sync user token; no race conditions, timing, or special configuration needed. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with the sync permission (not site admin, not internal sync) in the event's creator organization is required. UI:N: No victim interaction is needed. VC:N: The sync user already has read access to the event; no additional confidentiality exposure. VI:H: The attacker can fully modify, delete, add, and unprotect event data, completely defeating the integrity guarantee of the protection mechanism. VA:N: No denial-of-service impact is evident. SC/SI/SA:N: No evidence in the patch of direct impact on subsequent systems; cross-instance impact via publish is possible but not explicitly addressed in the patch evidence.
Weakness rationale
- CWE-862 The event protection authorization check was present only on the events/edit route. All other write endpoints (attributes, objects, populate, publish, unprotect, tags, reports, galaxy clusters, cryptographic keys) lacked the equivalent check, allowing a sync user to bypass the protection mechanism entirely.
- CWE-285 The authorization logic did not correctly account for the combination of sync-user role and event protection state across all code paths, resulting in an inconsistent enforcement of the protection policy.
Attack pattern rationale
- CAPEC-66 The access control policy for protected events was incorrectly configured: the protection check was applied to only one of many write endpoints. An attacker with a valid sync user account exploited the missing checks on the remaining endpoints to modify protected events. This is the closest CAPEC to the observed pattern of a partially enforced access control rule. Uncertainty: CAPEC-66 is a broad category; a more specific sub-pattern for 'inconsistent authorization enforcement across endpoints' does not exist in the CAPEC taxonomy, so this is the best available match.
Assumptions to verify
- Affected version range is unspecified; the patch does not include version tags or release boundaries. All MISP versions prior to this commit are assumed affected.
- CVSS SI (subsequent system integrity) is set to N. In practice, a modified protected event could be published to other MISP instances, potentially affecting them, but the patch does not explicitly address or evidence this cross-instance impact.
- CAPEC-66 is the closest available mapping; no CAPEC specifically covers 'inconsistent authorization enforcement across multiple endpoints of the same application'.
- The assumption that the attacker must belong to the same organization as the event creator (orgc_id match) is based on the existing perm_modify_org and perm_publish checks that were already present; the new check is an additional gate on top of those.
- The Co-Authored-By line references an AI assistant (Claude Opus 5.5); it is listed as a tool credit rather than a human remediation developer.
- The commit date (2026-11-11) is taken at face value from the patch metadata.
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-11 12:12 UTC Fix developed Corrective change authored (e4fa7371938d51840ad098e3f727b74f1b5b0831): fix: [security] Sync users change protected events only https://github.com/MISP/MISP/commit/e4fa73719.patch
- 2026-11-19 13:49 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/e4fa73719.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133163",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:24:34.101519Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:25:18.823Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"ACLComponent",
"EventsController",
"TagsController",
"CryptographicKeysController",
"Event model",
"EventReport model",
"Galaxy model",
"MispAttribute model"
],
"product": "misp",
"programFiles": [
"app/Controller/Component/ACLComponent.php",
"app/Controller/CryptographicKeysController.php",
"app/Controller/EventsController.php",
"app/Controller/TagsController.php",
"app/Model/Event.php",
"app/Model/EventReport.php",
"app/Model/Galaxy.php",
"app/Model/MispAttribute.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": "CERT.pl"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "tool",
"value": "Claude Opus 5.5"
}
],
"descriptions": [
{
"lang": "en",
"value": "MISP contains an authorization bypass affecting the event protection mechanism. In MISP, a protected event is designed to be modifiable only through the events/edit endpoint with a valid cryptographic signature. However, the protection check was enforced solely on that single route. All other write endpoints that operate on an event\u2014attributes (add, edit, delete), objects (delete), events (populate, publish, unprotect, upload_sample, upload_analysis_file), tags (attach, detach), event reports (edit, delete), galaxy clusters (attach, detach), and cryptographic keys (add, delete)\u2014lacked the equivalent check.\n\nAs a result, an authenticated user holding the sync permission (perm_sync) who is neither a site administrator nor an internal sync user (perm_sync_internal), and who belongs to the same organization as the event\u0027s creator (orgc_id), could modify, delete, or add data to a protected event without providing a valid signature. This included the ability to unprotect the event entirely, publish it to other instances, and add cryptographic signing keys that would subsequently permit signed edits, effectively nullifying the protection mechanism.\n\nThe vulnerability requires an authenticated sync user account within the event\u0027s creator organization. No user interaction or special network conditions are required; standard API calls to the affected endpoints are sufficient. The security impact is a loss of integrity over protected threat-intelligence events: an attacker can inject, alter, or remove attributes, objects, tags, reports, and galaxy cluster associations, and can remove the protection flag or add signing keys to enable persistent unauthorized modification."
}
],
"impacts": [
{
"capecId": "CAPEC-66",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-66 Exploiting Incorrectly Configured Access Control"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW",
"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-19T13:50:03Z",
"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-285",
"description": "CWE-285 Improper Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T13:55:15.729Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/e4fa73719"
}
],
"solutions": [
{
"lang": "en",
"value": "A shared authorization check (isProtectedFromSyncUser / assertNotProtectedFromSyncUser) was introduced in the Event model and enforced across all write paths. The check denies any non-internal, non-site-admin sync user from modifying a protected event through any route other than events/edit with a valid signature. The check is now invoked in the ACL component (modify, publish, tag), in the CryptographicKeys, Events, and Tags controllers, and in the Event, EventReport, Galaxy, and MispAttribute models, closing every previously unprotected write path."
}
],
"title": "MISP: External Sync User Can Modify Protected Events Without Signature via Multiple Write Routes",
"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": [
"Affected version range is unspecified; the patch does not include version tags or release boundaries. All MISP versions prior to this commit are assumed affected.",
"CVSS SI (subsequent system integrity) is set to N. In practice, a modified protected event could be published to other MISP instances, potentially affecting them, but the patch does not explicitly address or evidence this cross-instance impact.",
"CAPEC-66 is the closest available mapping; no CAPEC specifically covers \u0027inconsistent authorization enforcement across multiple endpoints of the same application\u0027.",
"The assumption that the attacker must belong to the same organization as the event creator (orgc_id match) is based on the existing perm_modify_org and perm_publish checks that were already present; the new check is an additional gate on top of those.",
"The Co-Authored-By line references an AI assistant (Claude Opus 5.5); it is listed as a tool credit rather than a human remediation developer.",
"The commit date (2026-11-11) is taken at face value from the patch metadata."
],
"capecRationale": [
{
"capecId": "CAPEC-66",
"rationale": "The access control policy for protected events was incorrectly configured: the protection check was applied to only one of many write endpoints. An attacker with a valid sync user account exploited the missing checks on the remaining endpoints to modify protected events. This is the closest CAPEC to the observed pattern of a partially enforced access control rule. Uncertainty: CAPEC-66 is a broad category; a more specific sub-pattern for \u0027inconsistent authorization enforcement across endpoints\u0027 does not exist in the CAPEC taxonomy, so this is the best available match."
}
],
"commit": "e4fa7371938d51840ad098e3f727b74f1b5b0831",
"confidence": "high",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "CERT.pl"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "tool",
"value": "Claude Opus 5.5"
}
],
"cvssRationale": "AV:N: MISP is a network-accessible web application. AC:L: Exploitation requires only standard API calls with a valid sync user token; no race conditions, timing, or special configuration needed. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with the sync permission (not site admin, not internal sync) in the event\u0027s creator organization is required. UI:N: No victim interaction is needed. VC:N: The sync user already has read access to the event; no additional confidentiality exposure. VI:H: The attacker can fully modify, delete, add, and unprotect event data, completely defeating the integrity guarantee of the protection mechanism. VA:N: No denial-of-service impact is evident. SC/SI/SA:N: No evidence in the patch of direct impact on subsequent systems; cross-instance impact via publish is possible but not explicitly addressed in the patch evidence.",
"draft": false,
"fixSummary": "A shared authorization check (isProtectedFromSyncUser / assertNotProtectedFromSyncUser) was introduced in the Event model and enforced across all write paths. The check denies any non-internal, non-site-admin sync user from modifying a protected event through any route other than events/edit with a valid signature. The check is now invoked in the ACL component (modify, publish, tag), in the CryptographicKeys, Events, and Tags controllers, and in the Event, EventReport, Galaxy, and MispAttribute models, closing every previously unprotected write path.",
"generatedAt": "2026-11-19T13:50:03.083744Z",
"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": "5b0f387b75bb90f531299281ed35699622c3525ee98bdfdad286cbf10af3bdca",
"patchSummary": "Added Event::isProtectedFromSyncUser() and Event::assertNotProtectedFromSyncUser() methods that return true / throw ForbiddenException when the user has perm_sync but lacks perm_site_admin and perm_sync_internal, and the target event has protected=1. Inserted calls to these methods in: ACLComponent::canModifyEvent(), canPublishEvent(), canModifyTag(); CryptographicKeysController::add() and delete(); EventsController::populate(), upload_sample(), upload_analysis_file(); TagsController::__findObjectByUuid(); Event::userCanModifyEvent() and upload_stix(); EventReport::fetchIfAuthorized(); Galaxy::detachCluster() and detachClusterByTagId(); MispAttribute::deleteAttribute(). Also added the \u0027protected\u0027 field to the event query in upload_sample. Added a comprehensive regression test class (ProtectedEventSyncWrites) covering all affected routes plus control tests for internal sync users, org admins, and post-unprotect behavior.",
"patchTruncated": false,
"patches": [
{
"commit": "e4fa7371938d51840ad098e3f727b74f1b5b0831",
"date": "Wed, 11 Nov 2026 13:12:32 +0100",
"patchSha256": "5b0f387b75bb90f531299281ed35699622c3525ee98bdfdad286cbf10af3bdca",
"retrievedAt": "2026-11-19T13:49:21.953367Z",
"source": "https://github.com/MISP/MISP/commit/e4fa73719.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/e4fa73719.patch",
"subject": "fix: [security] Sync users change protected events only"
}
],
"source": "https://github.com/MISP/MISP/commit/e4fa73719.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T13:50:03Z",
"version": "2.0.3"
},
"subject": "fix: [security] Sync users change protected events only",
"weaknessRationale": [
{
"cweId": "CWE-862",
"rationale": "The event protection authorization check was present only on the events/edit route. All other write endpoints (attributes, objects, populate, publish, unprotect, tags, reports, galaxy clusters, cryptographic keys) lacked the equivalent check, allowing a sync user to bypass the protection mechanism entirely."
},
{
"cweId": "CWE-285",
"rationale": "The authorization logic did not correctly account for the combination of sync-user role and event protection state across all code paths, resulting in an inconsistent enforcement of the protection policy."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (e4fa7371938d51840ad098e3f727b74f1b5b0831): fix: [security] Sync users change protected events only",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/e4fa73719.patch"
],
"timestamp": "2026-11-11T12:12: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/e4fa73719.patch"
],
"timestamp": "2026-11-19T13:49:21.953367Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20180"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133163",
"datePublished": "2026-11-19T13:55:15.729Z",
"dateReserved": "2026-11-19T13:55:10.863Z",
"dateUpdated": "2026-11-19T14:25:18.823Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133157 (GCVE-0-2026-133157)
Vulnerability from cvelistv5 – Published: 2026-11-19 13:42 – Updated: 2026-11-19 14:25| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/25a… | 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 14:21 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch
985a4b0d9641… - Confidence
- high
| Commit | Subject | Patch SHA-256 |
|---|---|---|
25ad65000e62
|
fix: [security] Neutralise formulas in audit log CSV exports | 985a4b0d9641… |
Fix summary
The audit log CSV export now routes all cell values through a shared literal-text formatter (csv_safe_cell) that neutralises formula-like content by prefixing it with an apostrophe, ensuring the text is treated as inert data when opened in a spreadsheet application. Typed numeric values and JSON exports remain unaffected.
Patch summary
In app/tools/audit_logs_core.py, the rows_to_csv function was modified to import and apply csv_safe_cell from ..utils/csv_utils to every cell value before writing to the CSV writer, replacing the previous raw value pass-through. The user manual (doc/user-manual.md) was updated to explicitly state that the formula-protection behaviour also applies to audit-log CSV exports.
CVSS rationale
AV:N because the attacker-influenced content enters via network traffic captured by flowintel. AC:L because crafting a formula-like string in logged data is straightforward. AT:N because no special race or timing conditions are required. PR:N because the attacker does not need an account in flowintel to generate traffic that is logged. UI:A because an administrator must actively open the CSV in a spreadsheet application for the formula to execute. VC/VI/VA are N because the flowintel application itself is not compromised. SC:L and SI:L reflect the potential for a spreadsheet formula to read or modify data in the adjacent spreadsheet context. SA:N because there is no evidence of availability impact on the adjacent component.
Weakness rationale
- CWE-1236 The vulnerability allows attacker-controlled text to be written into a CSV file without neutralisation, so that spreadsheet applications interpret the text as executable formulas. This is the precise definition of formula injection.
- CWE-74 The CSV output is consumed by a downstream component (spreadsheet application) that interprets special characters (leading =, +, -, @) as formula delimiters. The product failed to neutralise these special elements before output.
Attack pattern rationale
- CAPEC-119 CAPEC-119 directly describes the technique of injecting malicious formulas or commands into CSV files that are later opened in spreadsheet applications. The patch evidence (attacker-influenced audit text becoming spreadsheet formulas in a CSV export) is a textbook instance of this attack pattern. No uncertainty in this mapping.
Assumptions to verify
- The affected version is recorded as '0' from the explicit context; no specific version range or fixed version is provided in the patch metadata.
- The assumption that the attacker can influence audit log content via network traffic is inferred from the commit message stating 'Attacker-influenced audit text'; the exact mechanism of influence is not detailed in the patch.
- CVSS impact on adjacent components (SC:L, SI:L) assumes the spreadsheet formula could read or modify data; the patch does not specify the exact capabilities of the injected formulas.
- The csv_safe_cell utility was introduced for a prior finding (F142) and is assumed to correctly neutralise all formula-triggering characters (=, +, -, @, tab, newline).
- CAPEC-119 mapping is considered high-confidence; no uncertainty noted.
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 |
8 | 11 | high | 5 |
- 2026-11-06 09:54 UTC Fix developed Corrective change authored (25ad65000e62ee68a1a3444aeec73bd258189951): fix: [security] Neutralise formulas in audit log CSV exports https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch
- 2026-11-18 14:20 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133157",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:25:45.666859Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:25:55.135Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/tools/audit_logs_core.py"
],
"product": "flowintel",
"programFiles": [
"app/tools/audit_logs_core.py"
],
"repo": "https://github.com/flowintel/flowintel",
"vendor": "flowintel",
"versions": [
{
"lessThanOrEqual": "4.0.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"descriptions": [
{
"lang": "en",
"value": "flowintel contains a CSV injection vulnerability in its audit log CSV export functionality. Attacker-influenced text recorded in audit logs could be interpreted as spreadsheet formulas when an administrator opened the exported CSV file in a spreadsheet application.\n\nThe vulnerable behavior allowed an attacker who could influence audit log content (for example by generating network traffic that is captured and logged) to embed formula-like strings (such as =CMD() or =HYPERLINK()) into audit entries. When the resulting CSV export was opened in a spreadsheet application, these strings could be executed as formulas, potentially leading to data exfiltration, data manipulation, or execution of further malicious actions within the spreadsheet context.\n\nPreconditions:\n- An attacker must be able to influence content that is recorded in flowintel audit logs.\n- An administrator or user must export the audit logs to CSV and open the file in a spreadsheet application that interprets formulas.\n\nSecurity impact:\n- Potential information disclosure from the spreadsheet or linked resources.\n- Potential integrity impact on data within the spreadsheet application.\n- No direct compromise of the flowintel application itself.\n\nAffected version: \u003c4.1.0"
}
],
"impacts": [
{
"capecId": "CAPEC-119",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-119 CSV Injection"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.1,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "LOW",
"subIntegrityImpact": "LOW",
"userInteraction": "ACTIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T14:21:08Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-1236",
"description": "CWE-1236 Formula Injection",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-74",
"description": "CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T13:42:58.758Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951"
}
],
"solutions": [
{
"lang": "en",
"value": "The audit log CSV export now routes all cell values through a shared literal-text formatter (csv_safe_cell) that neutralises formula-like content by prefixing it with an apostrophe, ensuring the text is treated as inert data when opened in a spreadsheet application. Typed numeric values and JSON exports remain unaffected."
}
],
"title": "CSV Formula Injection in Audit Log CSV Exports in flowintel",
"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 version is recorded as \u00270\u0027 from the explicit context; no specific version range or fixed version is provided in the patch metadata.",
"The assumption that the attacker can influence audit log content via network traffic is inferred from the commit message stating \u0027Attacker-influenced audit text\u0027; the exact mechanism of influence is not detailed in the patch.",
"CVSS impact on adjacent components (SC:L, SI:L) assumes the spreadsheet formula could read or modify data; the patch does not specify the exact capabilities of the injected formulas.",
"The csv_safe_cell utility was introduced for a prior finding (F142) and is assumed to correctly neutralise all formula-triggering characters (=, +, -, @, tab, newline).",
"CAPEC-119 mapping is considered high-confidence; no uncertainty noted."
],
"capecRationale": [
{
"capecId": "CAPEC-119",
"rationale": "CAPEC-119 directly describes the technique of injecting malicious formulas or commands into CSV files that are later opened in spreadsheet applications. The patch evidence (attacker-influenced audit text becoming spreadsheet formulas in a CSV export) is a textbook instance of this attack pattern. No uncertainty in this mapping."
}
],
"commit": "25ad65000e62ee68a1a3444aeec73bd258189951",
"confidence": "high",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:N because the attacker-influenced content enters via network traffic captured by flowintel. AC:L because crafting a formula-like string in logged data is straightforward. AT:N because no special race or timing conditions are required. PR:N because the attacker does not need an account in flowintel to generate traffic that is logged. UI:A because an administrator must actively open the CSV in a spreadsheet application for the formula to execute. VC/VI/VA are N because the flowintel application itself is not compromised. SC:L and SI:L reflect the potential for a spreadsheet formula to read or modify data in the adjacent spreadsheet context. SA:N because there is no evidence of availability impact on the adjacent component.",
"fixSummary": "The audit log CSV export now routes all cell values through a shared literal-text formatter (csv_safe_cell) that neutralises formula-like content by prefixing it with an apostrophe, ensuring the text is treated as inert data when opened in a spreadsheet application. Typed numeric values and JSON exports remain unaffected.",
"generatedAt": "2026-11-18T14:21:08.189351Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 5,
"confidence": "high",
"model": "qwen3.8:27b",
"score": 8
}
],
"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": "985a4b0d9641681ef352721b0b961fbf7910ea60989bc6e6d422ca72ea285a6c",
"patchSummary": "In app/tools/audit_logs_core.py, the rows_to_csv function was modified to import and apply csv_safe_cell from ..utils/csv_utils to every cell value before writing to the CSV writer, replacing the previous raw value pass-through. The user manual (doc/user-manual.md) was updated to explicitly state that the formula-protection behaviour also applies to audit-log CSV exports.",
"patchTruncated": false,
"patches": [
{
"commit": "25ad65000e62ee68a1a3444aeec73bd258189951",
"date": "Fri, 6 Nov 2026 10:54:28 +0100",
"patchSha256": "985a4b0d9641681ef352721b0b961fbf7910ea60989bc6e6d422ca72ea285a6c",
"retrievedAt": "2026-11-18T14:20:43.501372Z",
"source": "https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch",
"subject": "fix: [security] Neutralise formulas in audit log CSV exports"
}
],
"source": "https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T14:21:08Z",
"version": "2.0.3"
},
"subject": "fix: [security] Neutralise formulas in audit log CSV exports",
"weaknessRationale": [
{
"cweId": "CWE-1236",
"rationale": "The vulnerability allows attacker-controlled text to be written into a CSV file without neutralisation, so that spreadsheet applications interpret the text as executable formulas. This is the precise definition of formula injection."
},
{
"cweId": "CWE-74",
"rationale": "The CSV output is consumed by a downstream component (spreadsheet application) that interprets special characters (leading =, +, -, @) as formula delimiters. The product failed to neutralise these special elements before output."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (25ad65000e62ee68a1a3444aeec73bd258189951): fix: [security] Neutralise formulas in audit log CSV exports",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch"
],
"timestamp": "2026-11-06T09:54:28Z",
"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/flowintel/flowintel/commit/25ad65000e62ee68a1a3444aeec73bd258189951.patch"
],
"timestamp": "2026-11-18T14:20:43.501372Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20314"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133157",
"datePublished": "2026-11-19T13:42:58.758Z",
"dateReserved": "2026-11-19T13:42:50.926Z",
"dateUpdated": "2026-11-19T14:25:55.135Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-22311 (GCVE-0-2026-22311)
Vulnerability from cvelistv5 – Published: 2026-11-19 11:54 – Updated: 2026-11-19 20:05| URL | Tags |
|---|---|
| https://www.jtl-software.com/de/security/sicherhe… | vendor-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| JTL-Software GmbH | JTL-Shop |
Affected:
5.8.0 , < 5.8.4
(semver)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-22311",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T20:05:45.659297Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T20:05:55.697Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "JTL-Shop",
"vendor": "JTL-Software GmbH",
"versions": [
{
"lessThan": "5.8.4",
"status": "affected",
"version": "5.8.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eThe failed-login limiter of the JTL-Wawi\nsynchronisation interface of JTL-Shop derives the client identity from the\nclient-controlled X-Forwarded-For header and counts requests without credentials as failed\nlogins. An unauthenticated remote attacker can block the synchronisation\nbetween JTL-Shop and JTL-Wawi with a few requests and repeat this\nindefinitely, so that orders are no longer handed over to JTL-Wawi. No data is disclosed\nand no code is\u0026nbsp;executed.\u003c/p\u003e"
}
],
"value": "The failed-login limiter of the JTL-Wawi\nsynchronisation interface of JTL-Shop derives the client identity from the\nclient-controlled X-Forwarded-For header and counts requests without credentials as failed\nlogins. An unauthenticated remote attacker can block the synchronisation\nbetween JTL-Shop and JTL-Wawi with a few requests and repeat this\nindefinitely, so that orders are no longer handed over to JTL-Wawi. No data is disclosed\nand no code is\u00a0executed."
}
],
"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"
}
]
},
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.7,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-348",
"description": "CWE-348 Use of less trusted source",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-645",
"description": "CWE-645 Overly restrictive account lockout mechanism",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T11:54:50.011Z",
"orgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"shortName": "ENISA"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://www.jtl-software.com/de/security/sicherheitshinweis-wawi-synchronisation_sperrung/"
}
],
"title": "Use of a less trusted source leading to denial of service by lockout in JTL-Shop",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"assignerShortName": "ENISA",
"cveId": "CVE-2026-22311",
"datePublished": "2026-11-19T11:54:50.011Z",
"dateReserved": "2026-01-07T09:31:00.563Z",
"dateUpdated": "2026-11-19T20:05:55.697Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-123058 (GCVE-0-2026-123058)
Vulnerability from cvelistv5 – Published: 2026-11-19 11:48 – Updated: 2026-11-19 20:05- CWE-306 - Missing authentication for critical function
| URL | Tags |
|---|---|
| https://www.jtl-software.com/de/security/sicherhe… | vendor-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| JTL-Software GmbH | JTL-Shop |
Affected:
5.5.0 , < 5.5.5
(semver)
Affected: 5.6.0 , < 5.6.6 (semver) Affected: 5.7.0 , < 5.7.6 (semver) Affected: 5.8.0 , < 5.8.4 (semver) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-123058",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T20:05:12.654230Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T20:05:21.964Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "JTL-Shop",
"vendor": "JTL-Software GmbH",
"versions": [
{
"lessThan": "5.5.5",
"status": "affected",
"version": "5.5.0",
"versionType": "semver"
},
{
"lessThan": "5.6.6",
"status": "affected",
"version": "5.6.0",
"versionType": "semver"
},
{
"lessThan": "5.7.6",
"status": "affected",
"version": "5.7.0",
"versionType": "semver"
},
{
"lessThan": "5.8.4",
"status": "affected",
"version": "5.8.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eThe web installer of JTL-Shop executes its\nstate-changing installation tasks without checking whether the shop is already\ninstalled, and was not removed or locked after the installation. An unauthenticated\nremote attacker who can\u0026nbsp;reach the installer directory can supply their own\ndatabase credentials, create\u0026nbsp;administrator and synchronisation accounts and\noverwrite the shop\u0026nbsp;configuration. This can lead to a full takeover of\nthe shop, including code\u0026nbsp;execution on the server.\u003c/p\u003e"
}
],
"value": "The web installer of JTL-Shop executes its\nstate-changing installation tasks without checking whether the shop is already\ninstalled, and was not removed or locked after the installation. An unauthenticated\nremote attacker who can\u00a0reach the installer directory can supply their own\ndatabase credentials, create\u00a0administrator and synchronisation accounts and\noverwrite the shop\u00a0configuration. This can lead to a full takeover of\nthe shop, including code\u00a0execution on the server."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "HIGH",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 9.2,
"baseSeverity": "CRITICAL",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-306",
"description": "CWE-306 Missing authentication for critical function",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T11:48:17.215Z",
"orgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"shortName": "ENISA"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://www.jtl-software.com/de/security/sicherheitshinweis-web-installer_nicht_gesperrt/"
}
],
"title": "Missing authentication for critical function in JTL-Shop",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"assignerShortName": "ENISA",
"cveId": "CVE-2026-123058",
"datePublished": "2026-11-19T11:48:17.215Z",
"dateReserved": "2026-11-05T08:44:32.621Z",
"dateUpdated": "2026-11-19T20:05:21.964Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-125060 (GCVE-0-2026-125060)
Vulnerability from cvelistv5 – Published: 2026-11-19 11:36 – Updated: 2026-11-19 19:55- CWE-639 - Authorization bypass through User-Controlled key
| URL | Tags |
|---|---|
| https://www.jtl-software.com/de/security/sicherhe… | vendor-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| JTL-Software GmbH | JTL-Shop |
Affected:
5.5.0 , < 5.5.5
(semver)
Affected: 5.6.0 , < 5.6.6 (semver) Affected: 5.7.0 , < 5.7.6 (semver) Affected: 5.8.0 , < 5.8.4 (semver) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-125060",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T19:54:50.615969Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T19:55:07.474Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "JTL-Shop",
"vendor": "JTL-Software GmbH",
"versions": [
{
"lessThan": "5.5.5",
"status": "affected",
"version": "5.5.0",
"versionType": "semver"
},
{
"lessThan": "5.6.6",
"status": "affected",
"version": "5.6.0",
"versionType": "semver"
},
{
"lessThan": "5.7.6",
"status": "affected",
"version": "5.7.0",
"versionType": "semver"
},
{
"lessThan": "5.8.4",
"status": "affected",
"version": "5.8.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eThe checkout of JTL-Shop stores the delivery address\nID submitted by the customer in the session and adopts it into the order\nwithout verifying that the address belongs to the ordering customer. A remote\nattacker with access to the checkout, including a guest, can thereby attach\nthe delivery address of another customer to their own order. Name and\naddress of the other customer, and depending on the shop configuration\nfurther contact data, then appear in the order confirmation and customer\naccount. As the IDs are sequential, addresses can be enumerated. Goods may\nalso be shipped to the wrong address.\u003c/p\u003e\n\n\n\n\n\n\u003cbr\u003e"
}
],
"value": "The checkout of JTL-Shop stores the delivery address\nID submitted by the customer in the session and adopts it into the order\nwithout verifying that the address belongs to the ordering customer. A remote\nattacker with access to the checkout, including a guest, can thereby attach\nthe delivery address of another customer to their own order. Name and\naddress of the other customer, and depending on the shop configuration\nfurther contact data, then appear in the order confirmation and customer\naccount. As the IDs are sequential, addresses can be enumerated. Goods may\nalso be shipped to the wrong address."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 8.2,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"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-11-19T11:36:40.929Z",
"orgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"shortName": "ENISA"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://www.jtl-software.com/de/security/sicherheitshinweis-lieferadressen-bestellprozess/"
}
],
"title": "Authorization bypass through user-controlled key in JTL-Shop",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"assignerShortName": "ENISA",
"cveId": "CVE-2026-125060",
"datePublished": "2026-11-19T11:36:40.929Z",
"dateReserved": "2026-11-09T16:33:23.763Z",
"dateUpdated": "2026-11-19T19:55:07.474Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-125061 (GCVE-0-2026-125061)
Vulnerability from cvelistv5 – Published: 2026-11-19 11:23 – Updated: 2026-11-19 17:18- CWE-79 - Improper neutralization of input during web page generation ('cross-site scripting')
| URL | Tags |
|---|---|
| https://www.jtl-software.com/de/security/sicherhe… | vendor-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| JTL-Software GmbH | JTL PayPal Checkout plugin (jtl_paypal_commerce) |
Affected:
1.2.0 , < 2.3.2
(semver)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-125061",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T17:18:01.305173Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T17:18:12.181Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "JTL PayPal Checkout plugin (jtl_paypal_commerce)",
"vendor": "JTL-Software GmbH",
"versions": [
{
"lessThan": "2.3.2",
"status": "affected",
"version": "1.2.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Elka\u00f1o"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eThe administration page \"Offene\nBestellungen\" (open orders) of the JTL PayPal Checkout plugin for JTL-Shop outputs the\ncustomer name of pending\u0026nbsp;orders without output encoding. A registered\ncustomer (free self-registration)\u0026nbsp;can submit an HTML-entity-encoded name, which is\ndecoded to markup when the billing address of an order is written. If\nthe PayPal payment is left unfinished, the order is listed on the page and the\nname is rendered as markup in the browser of an administrator who opens\nthe page. The script code runs with the privileges of that administrator\nand can, for example, create a new administrator account. Guest orders are\nnot affected, because\u0026nbsp;the name is encoded again.\u003c/p\u003e"
}
],
"value": "The administration page \"Offene\nBestellungen\" (open orders) of the JTL PayPal Checkout plugin for JTL-Shop outputs the\ncustomer name of pending\u00a0orders without output encoding. A registered\ncustomer (free self-registration)\u00a0can submit an HTML-entity-encoded name, which is\ndecoded to markup when the billing address of an order is written. If\nthe PayPal payment is left unfinished, the order is listed on the page and the\nname is rendered as markup in the browser of an administrator who opens\nthe page. The script code runs with the privileges of that administrator\nand can, for example, create a new administrator account. Guest orders are\nnot affected, because\u00a0the name is encoded again."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 8.7,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.5,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-79",
"description": "CWE-79 Improper neutralization of input during web page generation (\u0027cross-site scripting\u0027)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T11:23:52.970Z",
"orgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"shortName": "ENISA"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://www.jtl-software.com/de/security/sicherheitshinweis-paypal-checkout-plugin_xss/"
}
],
"title": "Stored cross-site scripting in the JTL PayPal Checkout plugin",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"assignerShortName": "ENISA",
"cveId": "CVE-2026-125061",
"datePublished": "2026-11-19T11:23:52.970Z",
"dateReserved": "2026-11-09T16:35:00.267Z",
"dateUpdated": "2026-11-19T17:18:12.181Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133001 (GCVE-0-2026-133001)
Vulnerability from cvelistv5 – Published: 2026-11-19 10:35 – Updated: 2026-11-19 17:16| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/c15… | 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 14:20 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch
408047b5b5e0… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
c158e1bdcebd
|
fix: [security] Refresh alert ownership scope on duplicate | 408047b5b5e0… |
Fix summary
The fix ensures that on every duplicate alert update, the ownership and visibility scope fields are unconditionally refreshed from the current connector scope, regardless of the alert's review status. This prevents alerts from retaining a stale, potentially broader visibility scope after the connector's scope has been narrowed or reassigned.
Patch summary
In app/alerting/alerting_core.py, within the _update_existing_alert function, two lines were added before the terminal-review-status conditional block: existing.owner_user_id and existing.owner_org_id are now assigned from the normalized incoming data on every duplicate update. Previously these fields were only set during initial alert creation and were not refreshed when a duplicate alert was ingested, leaving the stale scope in place.
CVSS rationale
AV:N - the platform is network-accessible. AC:L - the vulnerability is inherent in the duplicate-update code path; no special race or timing is needed. AT:N - no manipulation of the attack target is required. PR:L - an authenticated user with prior access to the alert is needed. UI:N - no user interaction beyond normal platform use. VC:L - confidential alert data is exposed to users outside the intended scope, but only for alerts affected by a scope change. VI:N, VA:N - no integrity or availability impact. SC:N, SI:N, SA:N - no secondary impacts. The overall severity is moderate: limited to a subset of alerts whose scope changed, requiring prior legitimate access.
Weakness rationale
- CWE-668 The alert resource remains exposed to a broader set of users/organizations (the wrong sphere) because the ownership/visibility fields are not updated when the connector scope changes. The resource is accessible to entities outside its intended authorization boundary.
- CWE-862 The system fails to enforce the current authorization scope on duplicate updates, effectively missing the authorization check that would restrict visibility to the correct set of users and organizations.
Attack pattern rationale
- CAPEC-10 The closest plausible attack pattern is leveraging a trusted relationship: a user or organization that previously had legitimate access to an alert (because it was within their scope) retains that access after the scope should have been narrowed. The attacker leverages the stale trust/visibility binding. This mapping is uncertain because the vulnerability is more of a stale-state authorization bug than an active exploitation of trust, but CAPEC-10 is the best available match for unauthorized access via a previously valid relationship.
Assumptions to verify
- The affected version range is not precisely specified in the patch metadata; the affected_version field contains '0' which is treated as a placeholder. All versions prior to commit c158e1bd are assumed affected.
- The CAPEC-10 mapping is the closest available match but the vulnerability is more accurately described as a stale-state authorization defect rather than an active exploitation of trust relationships.
- The severity of the confidentiality impact (VC:L) assumes that the exposed alert content is sensitive but that the exposure is limited to a subset of alerts whose scope changed; if all alerts are affected or contain highly sensitive data, VC could be rated Higher.
- The platform is assumed to be a multi-tenant or multi-organization security alerting system where visibility scoping is a core authorization mechanism.
- No evidence of active exploitation or public PoC was found in the patch or metadata.
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 | medium | 5 |
- 2026-11-06 09:54 UTC Fix developed Corrective change authored (c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362): fix: [security] Refresh alert ownership scope on duplicate https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch
- 2026-11-18 14:20 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133001",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T17:16:15.912845Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T17:16:23.842Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/alerting/alerting_core.py"
],
"product": "flowintel",
"programFiles": [
"app/alerting/alerting_core.py"
],
"repo": "https://github.com/flowintel/flowintel",
"vendor": "flowintel",
"versions": [
{
"lessThanOrEqual": "4.0.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"descriptions": [
{
"lang": "en",
"value": "FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector\u0027s current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector\u0027s scope was narrowed or changed.\n\nThis means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.\n\nSecurity impact:\n- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.\n- Stale access persists indefinitely until the alert is independently re-scoped or deleted.\n\nAffected version: \u003c4.1.0."
}
],
"impacts": [
{
"capecId": "CAPEC-10",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-10 Leveraging Trusted Relationships"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T14:20:42Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "CWE-668 Exposure of Resource to Wrong Sphere",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-862",
"description": "CWE-862 Missing Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T10:35:06.740Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix ensures that on every duplicate alert update, the ownership and visibility scope fields are unconditionally refreshed from the current connector scope, regardless of the alert\u0027s review status. This prevents alerts from retaining a stale, potentially broader visibility scope after the connector\u0027s scope has been narrowed or reassigned."
}
],
"title": "FlowIntel Alert Visibility Scope Not Refreshed on Duplicate Ingestion",
"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 version range is not precisely specified in the patch metadata; the affected_version field contains \u00270\u0027 which is treated as a placeholder. All versions prior to commit c158e1bd are assumed affected.",
"The CAPEC-10 mapping is the closest available match but the vulnerability is more accurately described as a stale-state authorization defect rather than an active exploitation of trust relationships.",
"The severity of the confidentiality impact (VC:L) assumes that the exposed alert content is sensitive but that the exposure is limited to a subset of alerts whose scope changed; if all alerts are affected or contain highly sensitive data, VC could be rated Higher.",
"The platform is assumed to be a multi-tenant or multi-organization security alerting system where visibility scoping is a core authorization mechanism.",
"No evidence of active exploitation or public PoC was found in the patch or metadata."
],
"capecRationale": [
{
"capecId": "CAPEC-10",
"rationale": "The closest plausible attack pattern is leveraging a trusted relationship: a user or organization that previously had legitimate access to an alert (because it was within their scope) retains that access after the scope should have been narrowed. The attacker leverages the stale trust/visibility binding. This mapping is uncertain because the vulnerability is more of a stale-state authorization bug than an active exploitation of trust, but CAPEC-10 is the best available match for unauthorized access via a previously valid relationship."
}
],
"commit": "c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:N - the platform is network-accessible. AC:L - the vulnerability is inherent in the duplicate-update code path; no special race or timing is needed. AT:N - no manipulation of the attack target is required. PR:L - an authenticated user with prior access to the alert is needed. UI:N - no user interaction beyond normal platform use. VC:L - confidential alert data is exposed to users outside the intended scope, but only for alerts affected by a scope change. VI:N, VA:N - no integrity or availability impact. SC:N, SI:N, SA:N - no secondary impacts. The overall severity is moderate: limited to a subset of alerts whose scope changed, requiring prior legitimate access.",
"fixSummary": "The fix ensures that on every duplicate alert update, the ownership and visibility scope fields are unconditionally refreshed from the current connector scope, regardless of the alert\u0027s review status. This prevents alerts from retaining a stale, potentially broader visibility scope after the connector\u0027s scope has been narrowed or reassigned.",
"generatedAt": "2026-11-18T14:20:42.931868Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 5,
"confidence": "medium",
"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": "408047b5b5e090f3bcc7d9a38dcd75dc8fcb0c3d982c82e1bc8a28e6c0f28f8d",
"patchSummary": "In app/alerting/alerting_core.py, within the _update_existing_alert function, two lines were added before the terminal-review-status conditional block: existing.owner_user_id and existing.owner_org_id are now assigned from the normalized incoming data on every duplicate update. Previously these fields were only set during initial alert creation and were not refreshed when a duplicate alert was ingested, leaving the stale scope in place.",
"patchTruncated": false,
"patches": [
{
"commit": "c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362",
"date": "Fri, 6 Nov 2026 10:54:31 +0100",
"patchSha256": "408047b5b5e090f3bcc7d9a38dcd75dc8fcb0c3d982c82e1bc8a28e6c0f28f8d",
"retrievedAt": "2026-11-18T14:20:07.629180Z",
"source": "https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch",
"subject": "fix: [security] Refresh alert ownership scope on duplicate"
}
],
"source": "https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T14:20:42Z",
"version": "2.0.3"
},
"subject": "fix: [security] Refresh alert ownership scope on duplicate",
"weaknessRationale": [
{
"cweId": "CWE-668",
"rationale": "The alert resource remains exposed to a broader set of users/organizations (the wrong sphere) because the ownership/visibility fields are not updated when the connector scope changes. The resource is accessible to entities outside its intended authorization boundary."
},
{
"cweId": "CWE-862",
"rationale": "The system fails to enforce the current authorization scope on duplicate updates, effectively missing the authorization check that would restrict visibility to the correct set of users and organizations."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362): fix: [security] Refresh alert ownership scope on duplicate",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch"
],
"timestamp": "2026-11-06T09:54:31Z",
"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/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch"
],
"timestamp": "2026-11-18T14:20:07.629180Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20317"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133001",
"datePublished": "2026-11-19T10:35:06.740Z",
"dateReserved": "2026-11-19T10:34:56.100Z",
"dateUpdated": "2026-11-19T17:16:23.842Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-82950 (GCVE-0-2026-82950)
Vulnerability from cvelistv5 – Published: 2026-11-19 10:33 – Updated: 2026-11-19 16:54- CWE-390 - Detection of Error Condition Without Action
| Vendor | Product | Version | |
|---|---|---|---|
| Onyx Cookware ApS | Nexsmart Guardian 2 (Alarm system) |
Affected:
0
(semver)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-82950",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T16:52:42.933494Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T16:54:54.934Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "affected",
"product": "Nexsmart Guardian 2 (Alarm system)",
"vendor": "Onyx Cookware ApS",
"versions": [
{
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Elias Lindstr\u00f6m"
},
{
"lang": "en",
"type": "coordinator",
"value": "CERT-SE"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eThe device only supports Wi-Fi protocols vulnerable to\ndeauthentication attacks (WEP/WPA/WPA2). Should any event which would typically\nbe logged to the user\u2019s mobile device (such as arming or disarming the alarm or\nany tamper events) be incurred whilst the device is temporarily disconnected\nfrom its Wi-Fi network (such as via a deauthentication attack), those alerts\nwill not be sent even after connection is regained.\u003c/p\u003e"
}
],
"value": "The device only supports Wi-Fi protocols vulnerable to\ndeauthentication attacks (WEP/WPA/WPA2). Should any event which would typically\nbe logged to the user\u2019s mobile device (such as arming or disarming the alarm or\nany tamper events) be incurred whilst the device is temporarily disconnected\nfrom its Wi-Fi network (such as via a deauthentication attack), those alerts\nwill not be sent even after connection is regained."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "ADJACENT",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-390",
"description": "CWE-390: Detection of Error Condition Without Action",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T10:33:17.907Z",
"orgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"shortName": "ENISA"
},
"references": [
{
"url": "https://medium.com/@enalindstrom/learning-iot-security-with-the-nexsmart-guardian-2-8028d55c430c"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003ci\u003e\u003cspan\u003eNexsmart reported suspending sales and described a phase-out of the current Guardian models.\u0026nbsp;\u003c/span\u003e\u003cspan\u003eIf you own an affected system and are concerned, contact Nexsmart \nthrough its official support channels and ask about any current \nremediation guidance.\u003c/span\u003e\u003c/i\u003e"
}
],
"value": "Nexsmart reported suspending sales and described a phase-out of the current Guardian models.\u00a0If you own an affected system and are concerned, contact Nexsmart \nthrough its official support channels and ask about any current \nremediation guidance."
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Alert suppression through deauthentication-induced notification failure",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"assignerShortName": "ENISA",
"cveId": "CVE-2026-82950",
"datePublished": "2026-11-19T10:33:17.907Z",
"dateReserved": "2026-08-31T12:26:22.054Z",
"dateUpdated": "2026-11-19T16:54:54.934Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-82949 (GCVE-0-2026-82949)
Vulnerability from cvelistv5 – Published: 2026-11-19 10:32 – Updated: 2026-11-19 15:10- CWE-319 - Cleartext Transmission of Sensitive Information
| Vendor | Product | Version | |
|---|---|---|---|
| Onyx Cookware ApS | Nexsmart Guardian 2 (Alarm system) |
Affected:
0
(semver)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-82949",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T15:10:44.258774Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T15:10:55.174Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "affected",
"product": "Nexsmart Guardian 2 (Alarm system)",
"vendor": "Onyx Cookware ApS",
"versions": [
{
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Elias Lindstr\u00f6m"
},
{
"lang": "en",
"type": "coordinator",
"value": "CERT-SE"
}
],
"datePublic": "2026-11-19T09:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eThe static codes used for information transmission\nthroughout the 433.92 MHz system of the Guardian 2 system allow an attacker in\nproximity to monitor the movements of users inside the premises where the\nsensors are set up. This is further aided by the fact that codes transmitted\nreveal sensor type, although sensor location cannot be inferred from this\ntraffic alone.\u003c/p\u003e"
}
],
"value": "The static codes used for information transmission\nthroughout the 433.92 MHz system of the Guardian 2 system allow an attacker in\nproximity to monitor the movements of users inside the premises where the\nsensors are set up. This is further aided by the fact that codes transmitted\nreveal sensor type, although sensor location cannot be inferred from this\ntraffic alone."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "ADJACENT",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-319",
"description": "CWE-319: Cleartext Transmission of Sensitive Information",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T10:32:13.090Z",
"orgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"shortName": "ENISA"
},
"references": [
{
"url": "https://medium.com/@enalindstrom/learning-iot-security-with-the-nexsmart-guardian-2-8028d55c430c"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003ci\u003e\u003cspan\u003eNexsmart reported suspending sales and described a phase-out of the current Guardian models.\u0026nbsp;\u003c/span\u003e\u003cspan\u003eIf you own an affected system and are concerned, contact Nexsmart \nthrough its official support channels and ask about any current \nremediation guidance.\u003c/span\u003e\u003c/i\u003e"
}
],
"value": "Nexsmart reported suspending sales and described a phase-out of the current Guardian models.\u00a0If you own an affected system and are concerned, contact Nexsmart \nthrough its official support channels and ask about any current \nremediation guidance."
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Occupancy monitoring via unencrypted RF communication",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"assignerShortName": "ENISA",
"cveId": "CVE-2026-82949",
"datePublished": "2026-11-19T10:32:13.090Z",
"dateReserved": "2026-08-31T12:26:22.054Z",
"dateUpdated": "2026-11-19T15:10:55.174Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-82948 (GCVE-0-2026-82948)
Vulnerability from cvelistv5 – Published: 2026-11-19 10:30 – Updated: 2026-11-19 15:10- CWE-294 - Authentication Bypass by Capture-replay
| Vendor | Product | Version | |
|---|---|---|---|
| Onyx Cookware ApS | Nexsmart Guardian 2 (Alarm system) |
Affected:
0
(semver)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-82948",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T15:10:15.653657Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T15:10:24.881Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "affected",
"product": "Nexsmart Guardian 2 (Alarm system)",
"vendor": "Onyx Cookware ApS",
"versions": [
{
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Elias Lindstr\u00f6m"
},
{
"lang": "en",
"type": "coordinator",
"value": "CERT-SE"
}
],
"datePublic": "2026-11-19T09:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eThe Guardian 2 alarm unit lacks a mechanism to\nauthenticate control commands sent over 433.92 MHz, which allows an attacker to\nreplay the static commands to impersonate activity.\u003cspan\u003e\u0026nbsp; \u003c/span\u003eThe attacker can also disarm or arm the\nsystem at will if a Nexsmart keypad (product link) is in use, thus compromising\nthe functionality of the alarm system completely.\u003c/p\u003e"
}
],
"value": "The Guardian 2 alarm unit lacks a mechanism to\nauthenticate control commands sent over 433.92 MHz, which allows an attacker to\nreplay the static commands to impersonate activity.\u00a0 The attacker can also disarm or arm the\nsystem at will if a Nexsmart keypad (product link) is in use, thus compromising\nthe functionality of the alarm system completely."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "ADJACENT",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-294",
"description": "CWE-294: Authentication Bypass by Capture-replay",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T10:30:43.109Z",
"orgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"shortName": "ENISA"
},
"references": [
{
"url": "https://medium.com/@enalindstrom/learning-iot-security-with-the-nexsmart-guardian-2-8028d55c430c"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003ci\u003e\u003cspan\u003eNexsmart reported suspending sales and described a phase-out of the current Guardian models.\u0026nbsp;\u003c/span\u003e\u003cspan\u003eIf you own an affected system and are concerned, contact Nexsmart \nthrough its official support channels and ask about any current \nremediation guidance.\u003c/span\u003e\u003c/i\u003e"
}
],
"value": "Nexsmart reported suspending sales and described a phase-out of the current Guardian models.\u00a0If you own an affected system and are concerned, contact Nexsmart \nthrough its official support channels and ask about any current \nremediation guidance."
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "RF Replay of control commands",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
"assignerShortName": "ENISA",
"cveId": "CVE-2026-82948",
"datePublished": "2026-11-19T10:30:43.109Z",
"dateReserved": "2026-08-31T12:26:22.054Z",
"dateUpdated": "2026-11-19T15:10:24.881Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-110462 (GCVE-0-2026-110462)
Vulnerability from cvelistv5 – Published: 2026-11-19 06:30 – Updated: 2026-11-19 15:00| URL | Tags |
|---|---|
| https://pro.comelitgroup.com/en-us/product/1456B | product |
| Vendor | Product | Version | |
|---|---|---|---|
| Comelit Group S.p.A. | 1456B Multi-User Gateway |
Affected:
0 , ≤ 2.10.0
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-110462",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:57:56.476043Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T15:00:16.837Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "affected",
"product": "1456B Multi-User Gateway",
"vendor": "Comelit Group S.p.A.",
"versions": [
{
"lessThanOrEqual": "2.10.0",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Teemu Tapanila"
},
{
"lang": "en",
"type": "finder",
"value": "Juha Jussila"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eThe Comelit 1456B Multi-User Gateway, in firmware versions up to and including 2.10.0, allows a user authenticated to the web interface with the Installer role to export a system configuration backup. The resulting backup file contains the configured passwords for all privileged roles\u003c/p\u003e"
}
],
"value": "The Comelit 1456B Multi-User Gateway, in firmware versions up to and including 2.10.0, allows a user authenticated to the web interface with the Installer role to export a system configuration backup. The resulting backup file contains the configured passwords for all privileged roles"
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.6,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-312",
"description": "CWE-312 Cleartext Storage of Sensitive Information",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-269",
"description": "CWE-269 Improper Privilege Management",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T06:30:51.842Z",
"orgId": "db4dfee8-a97e-4877-bfae-eba6d14a2166",
"shortName": "NCSC-FI"
},
"references": [
{
"tags": [
"product"
],
"url": "https://pro.comelitgroup.com/en-us/product/1456B"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "Comelit 1456B Multi-User Gateway exposes all role passwords in cleartext via Installer-accessible backup",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "db4dfee8-a97e-4877-bfae-eba6d14a2166",
"assignerShortName": "NCSC-FI",
"cveId": "CVE-2026-110462",
"datePublished": "2026-11-19T06:30:51.842Z",
"dateReserved": "2026-10-14T06:06:47.280Z",
"dateUpdated": "2026-11-19T15:00:16.837Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-110461 (GCVE-0-2026-110461)
Vulnerability from cvelistv5 – Published: 2026-11-19 06:28 – Updated: 2026-11-19 14:57- CWE-1392 - Use of Default Credentials
| URL | Tags |
|---|---|
| https://pro.comelitgroup.com/en-us/product/1456B | product |
| Vendor | Product | Version | |
|---|---|---|---|
| Comelit Group S.p.A. | 1456B Multi-User Gateway |
Affected:
0 , ≤ 2.10.0
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-110461",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:56:50.943133Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:57:01.762Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "affected",
"product": "1456B Multi-User Gateway",
"vendor": "Comelit Group S.p.A.",
"versions": [
{
"lessThanOrEqual": "2.10.0",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Teemu Tapanila"
},
{
"lang": "en",
"type": "finder",
"value": "Juha Jussila"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eThe Comelit 1456B Multi-User Gateway, in firmware versions up to and including 2.10.0, is configured with static default passwords for multiple privileged roles. None of these passwords are required to be changed during initial configuration, and they remain at their default values unless the administrator changes them manually. An attacker with network access to the device can authenticate using these default credentials and gain administrative control.\u003c/p\u003e"
}
],
"value": "The Comelit 1456B Multi-User Gateway, in firmware versions up to and including 2.10.0, is configured with static default passwords for multiple privileged roles. None of these passwords are required to be changed during initial configuration, and they remain at their default values unless the administrator changes them manually. An attacker with network access to the device can authenticate using these default credentials and gain administrative control."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 9.3,
"baseSeverity": "CRITICAL",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-1392",
"description": "CWE-1392 Use of Default Credentials",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T06:28:27.781Z",
"orgId": "db4dfee8-a97e-4877-bfae-eba6d14a2166",
"shortName": "NCSC-FI"
},
"references": [
{
"tags": [
"product"
],
"url": "https://pro.comelitgroup.com/en-us/product/1456B"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "Comelit 1456B Multi-User Gateway ships with default administrative credentials",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "db4dfee8-a97e-4877-bfae-eba6d14a2166",
"assignerShortName": "NCSC-FI",
"cveId": "CVE-2026-110461",
"datePublished": "2026-11-19T06:28:27.781Z",
"dateReserved": "2026-10-14T06:06:45.832Z",
"dateUpdated": "2026-11-19T14:57:01.762Z",
"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-132643 (GCVE-0-2026-132643)
Vulnerability from cvelistv5 – Published: 2026-11-18 21:08 – Updated: 2026-11-18 21:25| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/415f07967 | 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:06 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/415f07967.patch
0eacdfd112fc… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
415f07967704
|
fix: [security] Anonymised sightings cannot be attributed | 0eacdfd112fc… |
Fix summary
A new authorization check (orgFilterAllowed) is introduced in the Sighting model. When Sightings_anonymise is enabled, a non-site-admin user's org_id filter targeting another organisation is rejected: listSightings returns an empty result set, and restSearch either skips the negated condition or substitutes an impossible value (-1) for the positive filter. Site administrators and users filtering by their own organisation retain full functionality. When anonymization is disabled, the filter behaves as before.
Patch summary
Adds a private method orgFilterAllowed() to app/Model/Sighting.php that returns true only when anonymization is off, the user is a site admin, or the org_id matches the user's own organisation. In listSightings(), an early return of an empty array is inserted when the filter is not allowed. In restSearch(), when the filter is not allowed, negated conditions are skipped (continue) and positive conditions are set to org_id = -1 to match nothing. A new regression test class SightingsAnonymisedOrgFilter in tests/testregressions.py validates that non-admins cannot unmask reporters via either endpoint, that site admins retain filter access, and that the filter remains functional when anonymization is disabled.
CVSS rationale
AV:N: MISP is a network-accessible web application; the vulnerable endpoints are HTTP APIs. AC:L: Exploitation requires only adding an org_id parameter to a standard API call; no race conditions, timing, or complex setup needed. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with perm_sighting (sighting read) is sufficient; site admin is not required. UI:N: No victim interaction is needed; the attacker simply calls the API. VC:L: The impact is limited to revealing which organisation reported a sighting; full record contents and other data remain protected. VI:N, VA:N: No integrity or availability impact. SC:N, SI:N, SA:N: No impact on subsequent components or safety.
Weakness rationale
- CWE-200 The primary impact is disclosure of the reporter's organisation identity, which the anonymization feature is designed to conceal. A non-privileged user can determine which organisation reported a sighting by filtering on that organisation's ID.
- CWE-862 The root cause is the absence of an authorization check on the org_id filter parameter. The endpoint accepted and applied any caller-supplied organisation ID without verifying whether the requesting user was permitted to filter by that organisation, especially in the context of anonymized sightings.
Attack pattern rationale
- CAPEC-66 The attacker manipulates the org_id request parameter to filter results by a specific organisation, thereby bypassing the anonymization control. This is the closest CAPEC to the observed attack: a legitimate parameter is used in a way that circumvents a security policy (anonymization). Uncertainty: this is not a classic parameter tampering (e.g., altering a price or ID to access another user's data) but rather exploiting a filter parameter to infer information that should be masked. No CAPEC specifically covers 'bypassing anonymization via filter parameter', so CAPEC-66 is the best available match.
Assumptions to verify
- The Sightings_anonymise setting must be enabled for the vulnerability to be exploitable; when disabled, the org_id filter is expected behavior and not a vulnerability.
- The user must have perm_sighting (sighting read permission) but must NOT be a site admin (perm_site_admin); site admins are explicitly allowed to filter by any organisation.
- The affected version range is unknown; the patch does not specify a version boundary. All versions of MISP with the Sightings_anonymise feature and the pre-fix listSightings/restSearch code are assumed affected.
- CAPEC-66 (Parameter Tampering) is the closest available attack pattern; no CAPEC specifically describes bypassing an anonymization control via a filter parameter, so this mapping carries uncertainty.
- CVSS PR:L assumes the attacker needs only a standard authenticated MISP user account with sighting read permissions; the exact minimum role is inferred from the test setup (least_privileged_role with perm_add and perm_sighting).
- The Co-Authored-By line references an AI assistant (Claude Opus 5.5); it is credited as a tool rather than a human remediation developer.
Model comparison
Selected qwen3.8:27b
by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.
| Model | Score | Agreement | Confidence | Assumptions |
|---|---|---|---|---|
qwen3.8:27b |
6 | 11 | medium | 6 |
- 2026-11-09 13:31 UTC Fix developed Corrective change authored (415f07967704bbc83b1c7ff599c913b752581457): fix: [security] Anonymised sightings cannot be attributed https://github.com/MISP/MISP/commit/415f07967.patch
- 2026-11-18 21:05 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/415f07967.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-132643",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T21:24:56.466463Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T21:25:04.425Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"Sighting model (app/Model/Sighting.php)",
"listSightings endpoint",
"sightings/restSearch endpoint"
],
"product": "misp",
"programFiles": [
"app/Model/Sighting.php"
],
"repo": "https://github.com/MISP/MISP",
"vendor": "misp",
"versions": [
{
"lessThanOrEqual": "2.5.51",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.5.51",
"versionStartIncluding": "0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "tool",
"value": "Claude Opus 5.5"
}
],
"descriptions": [
{
"lang": "en",
"value": "MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter\u0027s organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation\u0027s ID in the filter. The query would then return only that organisation\u0027s sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA."
}
],
"impacts": [
{
"capecId": "CAPEC-66",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-66 Parameter Tampering"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T21:06:20Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-200",
"description": "CWE-200 Exposure of Sensitive Information to an Unauthorized Actor",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-862",
"description": "CWE-862 Missing Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T21:08:37.441Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/415f07967"
}
],
"solutions": [
{
"lang": "en",
"value": "A new authorization check (orgFilterAllowed) is introduced in the Sighting model. When Sightings_anonymise is enabled, a non-site-admin user\u0027s org_id filter targeting another organisation is rejected: listSightings returns an empty result set, and restSearch either skips the negated condition or substitutes an impossible value (-1) for the positive filter. Site administrators and users filtering by their own organisation retain full functionality. When anonymization is disabled, the filter behaves as before."
}
],
"title": "MISP Anonymised Sightings Reporter Identity Disclosure via Organisation Filter",
"x_gcve": [
{
"extensions": {
"bcp-05-x-01": {
"ai_annotations": [
{
"ai_level": "generated",
"description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
"gna_source": 1,
"models": [
{
"gna_source": 1,
"identifier": "qwen3.8:27b",
"name": "qwen3.8:27b",
"source": "ollama"
}
],
"review_status": "full",
"scope": "record",
"tags": [
"ai-computer-assisted:llm-generated",
"ai-computer-assisted:classification"
]
}
]
},
"bcp-05-x-02": {
"x_patch2vuln": {
"assumptions": [
"The Sightings_anonymise setting must be enabled for the vulnerability to be exploitable; when disabled, the org_id filter is expected behavior and not a vulnerability.",
"The user must have perm_sighting (sighting read permission) but must NOT be a site admin (perm_site_admin); site admins are explicitly allowed to filter by any organisation.",
"The affected version range is unknown; the patch does not specify a version boundary. All versions of MISP with the Sightings_anonymise feature and the pre-fix listSightings/restSearch code are assumed affected.",
"CAPEC-66 (Parameter Tampering) is the closest available attack pattern; no CAPEC specifically describes bypassing an anonymization control via a filter parameter, so this mapping carries uncertainty.",
"CVSS PR:L assumes the attacker needs only a standard authenticated MISP user account with sighting read permissions; the exact minimum role is inferred from the test setup (least_privileged_role with perm_add and perm_sighting).",
"The Co-Authored-By line references an AI assistant (Claude Opus 5.5); it is credited as a tool rather than a human remediation developer."
],
"capecRationale": [
{
"capecId": "CAPEC-66",
"rationale": "The attacker manipulates the org_id request parameter to filter results by a specific organisation, thereby bypassing the anonymization control. This is the closest CAPEC to the observed attack: a legitimate parameter is used in a way that circumvents a security policy (anonymization). Uncertainty: this is not a classic parameter tampering (e.g., altering a price or ID to access another user\u0027s data) but rather exploiting a filter parameter to infer information that should be masked. No CAPEC specifically covers \u0027bypassing anonymization via filter parameter\u0027, so CAPEC-66 is the best available match."
}
],
"commit": "415f07967704bbc83b1c7ff599c913b752581457",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "tool",
"value": "Claude Opus 5.5"
}
],
"cvssRationale": "AV:N: MISP is a network-accessible web application; the vulnerable endpoints are HTTP APIs. AC:L: Exploitation requires only adding an org_id parameter to a standard API call; no race conditions, timing, or complex setup needed. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with perm_sighting (sighting read) is sufficient; site admin is not required. UI:N: No victim interaction is needed; the attacker simply calls the API. VC:L: The impact is limited to revealing which organisation reported a sighting; full record contents and other data remain protected. VI:N, VA:N: No integrity or availability impact. SC:N, SI:N, SA:N: No impact on subsequent components or safety.",
"draft": false,
"fixSummary": "A new authorization check (orgFilterAllowed) is introduced in the Sighting model. When Sightings_anonymise is enabled, a non-site-admin user\u0027s org_id filter targeting another organisation is rejected: listSightings returns an empty result set, and restSearch either skips the negated condition or substitutes an impossible value (-1) for the positive filter. Site administrators and users filtering by their own organisation retain full functionality. When anonymization is disabled, the filter behaves as before.",
"generatedAt": "2026-11-18T21:06:20.520780Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 6,
"confidence": "medium",
"model": "qwen3.8:27b",
"score": 6
}
],
"selectedModel": "qwen3.8:27b",
"selectionMethod": "deterministic-consensus-v1",
"selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
},
"patchSha256": "0eacdfd112fcbdac0e7bc2baacaaaec68d1bc5dc84f466b7adc8b54f695234e9",
"patchSummary": "Adds a private method orgFilterAllowed() to app/Model/Sighting.php that returns true only when anonymization is off, the user is a site admin, or the org_id matches the user\u0027s own organisation. In listSightings(), an early return of an empty array is inserted when the filter is not allowed. In restSearch(), when the filter is not allowed, negated conditions are skipped (continue) and positive conditions are set to org_id = -1 to match nothing. A new regression test class SightingsAnonymisedOrgFilter in tests/testregressions.py validates that non-admins cannot unmask reporters via either endpoint, that site admins retain filter access, and that the filter remains functional when anonymization is disabled.",
"patchTruncated": false,
"patches": [
{
"commit": "415f07967704bbc83b1c7ff599c913b752581457",
"date": "Mon, 9 Nov 2026 14:31:56 +0100",
"patchSha256": "0eacdfd112fcbdac0e7bc2baacaaaec68d1bc5dc84f466b7adc8b54f695234e9",
"retrievedAt": "2026-11-18T21:05:44.744740Z",
"source": "https://github.com/MISP/MISP/commit/415f07967.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/415f07967.patch",
"subject": "fix: [security] Anonymised sightings cannot be attributed"
}
],
"source": "https://github.com/MISP/MISP/commit/415f07967.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T21:06:20Z",
"version": "2.0.3"
},
"subject": "fix: [security] Anonymised sightings cannot be attributed",
"weaknessRationale": [
{
"cweId": "CWE-200",
"rationale": "The primary impact is disclosure of the reporter\u0027s organisation identity, which the anonymization feature is designed to conceal. A non-privileged user can determine which organisation reported a sighting by filtering on that organisation\u0027s ID."
},
{
"cweId": "CWE-862",
"rationale": "The root cause is the absence of an authorization check on the org_id filter parameter. The endpoint accepted and applied any caller-supplied organisation ID without verifying whether the requesting user was permitted to filter by that organisation, especially in the context of anonymized sightings."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (415f07967704bbc83b1c7ff599c913b752581457): fix: [security] Anonymised sightings cannot be attributed",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/415f07967.patch"
],
"timestamp": "2026-11-09T13:31:56Z",
"type": "fix-developed"
},
{
"description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
"id": "evt-fix-available-1",
"references": [
"https://github.com/MISP/MISP/commit/415f07967.patch"
],
"timestamp": "2026-11-18T21:05:44.744740Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20282"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-132643",
"datePublished": "2026-11-18T21:08:37.441Z",
"dateReserved": "2026-11-18T21:08:33.062Z",
"dateUpdated": "2026-11-18T21:25:04.425Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-132642 (GCVE-0-2026-132642)
Vulnerability from cvelistv5 – Published: 2026-11-18 21:04 – Updated: 2026-11-18 21:25| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/de1a25aa0 | 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:02 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/de1a25aa0.patch
1c33ce45dacf… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
de1a25aa0d27
|
fix: [security] Tag endpoints only act on events and | 1c33ce45dacf… |
Fix summary
The tag endpoints now load their target event or attribute using ACL-aware fetch methods (fetchSimpleEvent, fetchAttributeSimple) that apply the calling user's visibility rules before returning the object. A hidden event or attribute now produces the same response as a non-existent one, eliminating both the tag-enumeration information leak and the ability of host-organisation users to modify tags on records they cannot see. A clarifying comment was added to ACLComponent::canModifyTag to document that the caller must load the object with visibility applied first.
Patch summary
In EventsController::addTag (single and bulk paths) and EventsController::removeTag, replaced unscoped $this->Event->find('first', ['recursive' => -1, ...]) calls with $this->Event->fetchSimpleEvent($this->Auth->user(), $id), and added an explicit empty-check in removeTag returning 'Invalid event.' for hidden targets. In AttributesController::removeTag, replaced $this->MispAttribute->find('first', ['recursive' => -1, ...]) with $this->MispAttribute->fetchAttributeSimple($this->Auth->user(), [...]). Added a documentation comment in ACLComponent::canModifyTag noting that the event or attribute must be loaded with the user's visibility applied before the check. Added a regression test class TagEndpointsHiddenTargets covering hidden-event tag enumeration, host-org tag add/remove on hidden and visible records, bulk addTag, and site-admin behaviour.
CVSS rationale
AV:N: MISP is a web application accessed over the network. AC:L: The attack requires only a standard API call with a known or guessable event/attribute ID; no race conditions or special timing. AT:N: No manipulation of the attack target is needed. PR:L: The attacker must be an authenticated user with at least the tagger role (perm_tagger) or host-organisation membership; this is a low-privilege requirement in MISP's role model. UI:N: No user interaction is required. VC:L: The removeTag endpoint leaks which tags are present on a hidden event, a limited confidentiality impact on metadata. VI:L: Host-org users can add or remove local tags on hidden events/attributes, a limited integrity impact on tag metadata. VA:N: No availability impact. SC/SI/SA:N: No impact on other systems or resources beyond the MISP instance.
Weakness rationale
- CWE-862 The tag endpoints performed tag add/remove operations on events and attributes without first verifying that the calling user had visibility (ACL) on the target object. The authorization check (canModifyTag) was applied to an unscoped object, effectively missing the visibility authorization step.
- CWE-200 The removeTag endpoint returned different responses for a tag present versus absent on a hidden event, leaking information about the tag set of records the user was not authorized to view.
Attack pattern rationale
- CAPEC-128 MISP implements a custom ACL/visibility system for events and attributes. The tag endpoints incorrectly implemented this access control by loading the target object without applying the user's visibility filter before performing the operation. The access control mechanism existed (canModifyTag) but was applied to an unscoped object, making it ineffective. This is the closest CAPEC to the observed pattern of a custom authorization check being bypassed due to incorrect implementation. Uncertainty: CAPEC-100 (Parameter Tampering) could also apply since the attacker supplies an ID of a record they cannot see, but the root cause is the missing visibility scoping in the server-side load, making CAPEC-128 the more precise match.
Assumptions to verify
- The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.
- PR:L assumes the attacker needs only the tagger role (perm_tagger) or host-org membership, which is a low-privilege role in MISP's model; the exact minimum role was inferred from the test setup.
- VC:L assumes the tag-enumeration information disclosure is a low confidentiality impact; if the tag names themselves are considered sensitive, the impact could be higher.
- CAPEC-128 was selected as the closest match; CAPEC-100 (Parameter Tampering) is a secondary candidate but the root cause is server-side missing visibility scoping rather than client-side parameter manipulation.
- The commit date (2026-11-10) and the presence of 'Claude Opus 5.5' as co-author are taken at face value from the patch metadata; no independent verification was performed.
- No specific MISP release version is identified as the first fixed version; the patch is a single commit without a tag or release reference.
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-10 09:53 UTC Fix developed Corrective change authored (de1a25aa0d273ce5efcd73e138f8fcdbff9a79b0): fix: [security] Tag endpoints only act on events and https://github.com/MISP/MISP/commit/de1a25aa0.patch
- 2026-11-18 21:01 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/de1a25aa0.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-132642",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T21:25:43.315584Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T21:25:48.929Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"EventsController (addTag, removeTag)",
"AttributesController (removeTag)",
"ACLComponent (canModifyTag)"
],
"product": "misp",
"programFiles": [
"app/Controller/EventsController.php",
"app/Controller/AttributesController.php",
"app/Controller/Component/ACLComponent.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"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "tool",
"value": "Claude Opus 5.5"
}
],
"descriptions": [
{
"lang": "en",
"value": "MISP contains an access control flaw in its tag management endpoints: events/addTag (single and bulk), events/removeTag, and attributes/removeTag. These endpoints loaded their target event or attribute using an unscoped database query (recursive = -1) that did not apply the calling user\u0027s ACL visibility rules. As a result, two distinct security issues existed: (1) Information disclosure: the removeTag endpoint returned different responses depending on whether a given tag was present on a hidden event, allowing an authenticated user to enumerate which tags were applied to events they had no visibility into. (2) Unauthorized modification: users belonging to the host organisation, who are permitted to set local tags on records they can see, could add or remove local tags on events and attributes they could not see, because the canModifyTag ACL check operated on the unscoped object without first verifying the caller\u0027s visibility. The fix replaces the unscoped find() calls with ACL-aware fetch methods (fetchSimpleEvent and fetchAttributeSimple) that apply the user\u0027s visibility before the object is returned, and adds an explicit empty-object check in removeTag so that a hidden event responds identically to a non-existent one. Affected components include the EventsController (addTag, removeTag), the AttributesController (removeTag), and the ACLComponent (canModifyTag). The vulnerability requires an authenticated user with at least the tagger role (perm_tagger) or host-organisation membership."
}
],
"impacts": [
{
"capecId": "CAPEC-128",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-128 Exploiting Incorrectly Implemented Custom Access Control"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "LOW",
"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:02:05Z",
"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-200",
"description": "CWE-200 Exposure of Sensitive Information",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T21:04:49.421Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/de1a25aa0"
}
],
"solutions": [
{
"lang": "en",
"value": "The tag endpoints now load their target event or attribute using ACL-aware fetch methods (fetchSimpleEvent, fetchAttributeSimple) that apply the calling user\u0027s visibility rules before returning the object. A hidden event or attribute now produces the same response as a non-existent one, eliminating both the tag-enumeration information leak and the ability of host-organisation users to modify tags on records they cannot see. A clarifying comment was added to ACLComponent::canModifyTag to document that the caller must load the object with visibility applied first."
}
],
"title": "MISP Tag Endpoints Bypass ACL Visibility, Allowing Unauthorized Tag Modification and Enumeration on Hidden Events",
"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 are assumed affected.",
"PR:L assumes the attacker needs only the tagger role (perm_tagger) or host-org membership, which is a low-privilege role in MISP\u0027s model; the exact minimum role was inferred from the test setup.",
"VC:L assumes the tag-enumeration information disclosure is a low confidentiality impact; if the tag names themselves are considered sensitive, the impact could be higher.",
"CAPEC-128 was selected as the closest match; CAPEC-100 (Parameter Tampering) is a secondary candidate but the root cause is server-side missing visibility scoping rather than client-side parameter manipulation.",
"The commit date (2026-11-10) and the presence of \u0027Claude Opus 5.5\u0027 as co-author are taken at face value from the patch metadata; no independent verification was performed.",
"No specific MISP release version is identified as the first fixed version; the patch is a single commit without a tag or release reference."
],
"capecRationale": [
{
"capecId": "CAPEC-128",
"rationale": "MISP implements a custom ACL/visibility system for events and attributes. The tag endpoints incorrectly implemented this access control by loading the target object without applying the user\u0027s visibility filter before performing the operation. The access control mechanism existed (canModifyTag) but was applied to an unscoped object, making it ineffective. This is the closest CAPEC to the observed pattern of a custom authorization check being bypassed due to incorrect implementation. Uncertainty: CAPEC-100 (Parameter Tampering) could also apply since the attacker supplies an ID of a record they cannot see, but the root cause is the missing visibility scoping in the server-side load, making CAPEC-128 the more precise match."
}
],
"commit": "de1a25aa0d273ce5efcd73e138f8fcdbff9a79b0",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "tool",
"value": "Claude Opus 5.5"
}
],
"cvssRationale": "AV:N: MISP is a web application accessed over the network. AC:L: The attack requires only a standard API call with a known or guessable event/attribute ID; no race conditions or special timing. AT:N: No manipulation of the attack target is needed. PR:L: The attacker must be an authenticated user with at least the tagger role (perm_tagger) or host-organisation membership; this is a low-privilege requirement in MISP\u0027s role model. UI:N: No user interaction is required. VC:L: The removeTag endpoint leaks which tags are present on a hidden event, a limited confidentiality impact on metadata. VI:L: Host-org users can add or remove local tags on hidden events/attributes, a limited integrity impact on tag metadata. VA:N: No availability impact. SC/SI/SA:N: No impact on other systems or resources beyond the MISP instance.",
"draft": false,
"fixSummary": "The tag endpoints now load their target event or attribute using ACL-aware fetch methods (fetchSimpleEvent, fetchAttributeSimple) that apply the calling user\u0027s visibility rules before returning the object. A hidden event or attribute now produces the same response as a non-existent one, eliminating both the tag-enumeration information leak and the ability of host-organisation users to modify tags on records they cannot see. A clarifying comment was added to ACLComponent::canModifyTag to document that the caller must load the object with visibility applied first.",
"generatedAt": "2026-11-18T21:02:05.506995Z",
"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": "1c33ce45dacf16eb8ba1b3a6d54bdace7725b3a135386fb9ce5ceab87f5849f3",
"patchSummary": "In EventsController::addTag (single and bulk paths) and EventsController::removeTag, replaced unscoped $this-\u003eEvent-\u003efind(\u0027first\u0027, [\u0027recursive\u0027 =\u003e -1, ...]) calls with $this-\u003eEvent-\u003efetchSimpleEvent($this-\u003eAuth-\u003euser(), $id), and added an explicit empty-check in removeTag returning \u0027Invalid event.\u0027 for hidden targets. In AttributesController::removeTag, replaced $this-\u003eMispAttribute-\u003efind(\u0027first\u0027, [\u0027recursive\u0027 =\u003e -1, ...]) with $this-\u003eMispAttribute-\u003efetchAttributeSimple($this-\u003eAuth-\u003euser(), [...]). Added a documentation comment in ACLComponent::canModifyTag noting that the event or attribute must be loaded with the user\u0027s visibility applied before the check. Added a regression test class TagEndpointsHiddenTargets covering hidden-event tag enumeration, host-org tag add/remove on hidden and visible records, bulk addTag, and site-admin behaviour.",
"patchTruncated": false,
"patches": [
{
"commit": "de1a25aa0d273ce5efcd73e138f8fcdbff9a79b0",
"date": "Tue, 10 Nov 2026 10:53:53 +0100",
"patchSha256": "1c33ce45dacf16eb8ba1b3a6d54bdace7725b3a135386fb9ce5ceab87f5849f3",
"retrievedAt": "2026-11-18T21:01:26.169880Z",
"source": "https://github.com/MISP/MISP/commit/de1a25aa0.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/de1a25aa0.patch",
"subject": "fix: [security] Tag endpoints only act on events and"
}
],
"source": "https://github.com/MISP/MISP/commit/de1a25aa0.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-18T21:02:05Z",
"version": "2.0.3"
},
"subject": "fix: [security] Tag endpoints only act on events and",
"weaknessRationale": [
{
"cweId": "CWE-862",
"rationale": "The tag endpoints performed tag add/remove operations on events and attributes without first verifying that the calling user had visibility (ACL) on the target object. The authorization check (canModifyTag) was applied to an unscoped object, effectively missing the visibility authorization step."
},
{
"cweId": "CWE-200",
"rationale": "The removeTag endpoint returned different responses for a tag present versus absent on a hidden event, leaking information about the tag set of records the user was not authorized to view."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (de1a25aa0d273ce5efcd73e138f8fcdbff9a79b0): fix: [security] Tag endpoints only act on events and",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/de1a25aa0.patch"
],
"timestamp": "2026-11-10T09:53:53Z",
"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/de1a25aa0.patch"
],
"timestamp": "2026-11-18T21:01:26.169880Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20181"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-132642",
"datePublished": "2026-11-18T21:04:49.421Z",
"dateReserved": "2026-11-18T21:04:45.661Z",
"dateUpdated": "2026-11-18T21:25:48.929Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}