{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-133190 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-133190 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-133190 is a medium-severity vulnerability in misp, published on 19 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-133190 and fix it if it is affected.\n\nWhat it is: CVE-2026-133190 is a medium-severity vulnerability in misp, published on 19 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-133190 in the wild and no public exploit code.\n\nAffected product: misp. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-133190/ (Markdown: https://insights.sbomify.com/CVE-2026-133190/index.md)","id":"CVE-2026-133190","markdown":"https://insights.sbomify.com/CVE-2026-133190/index.md","name":"CVE-2026-133190","record":{"aliases":["GHSA-pfmx-9j63-82v6"],"analysis":null,"analysis_generated_by":null,"assigner":"CIRCL","component":null,"cpe":[{"criteria":[{"cpe":"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*","source":"cna","version_end_including":"2.5.51"}],"n_criteria":1,"name":null,"product":"misp","vendor":"misp"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"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"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"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's 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('first') instead of find('all')) 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"MISP, a threat intelligence sharing platform, contains a vulnerability in its cryptographic key management for protected (PGP-signed) events.","id":"CVE-2026-133190","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"In JetBrains Junie GitHub Action before 1.10.0 untrusted fork code could be processed in privileged workflow runs","id":"CVE-2026-133192"},"nickname":null,"packages":[],"prev":{"headline":"A command injection vulnerability was found in OpenStack Cinder's SSH-based storage-driver support.","id":"CVE-2026-133189"},"products":["misp"],"published":"2026-11-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","text_fixes":[],"updated":"2026-11-19","vendor_status":[],"vendors":["misp"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-133190/"}