@blamejs/exceptd-skills 0.13.72 → 0.13.74

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1037,7 +1037,10 @@
1037
1037
  ],
1038
1038
  "reference_url": "https://atlas.mitre.org/techniques/AML.T0104",
1039
1039
  "stix_id": "attack-pattern--04842d98-bb69-586e-9765-6ff1f56ef722",
1040
- "is_subtechnique": false
1040
+ "is_subtechnique": false,
1041
+ "cve_refs": [
1042
+ "CVE-2025-54136"
1043
+ ]
1041
1044
  },
1042
1045
  "AML.T0105": {
1043
1046
  "id": "AML.T0105",
@@ -2379,7 +2382,10 @@
2379
2382
  "ATLAS"
2380
2383
  ],
2381
2384
  "stix_id": "attack-pattern--b1b2cc5a-7312-5f26-93d3-8b8ee1baf97d",
2382
- "is_subtechnique": false
2385
+ "is_subtechnique": false,
2386
+ "cve_refs": [
2387
+ "CVE-2025-54136"
2388
+ ]
2383
2389
  },
2384
2390
  "AML.T0111": {
2385
2391
  "id": "AML.T0111",
@@ -272,7 +272,9 @@
272
272
  "CVE-2025-1094",
273
273
  "CVE-2025-11837",
274
274
  "CVE-2025-34291",
275
+ "CVE-2025-49596",
275
276
  "CVE-2025-53773",
277
+ "CVE-2025-54136",
276
278
  "CVE-2025-55319",
277
279
  "CVE-2025-68664",
278
280
  "CVE-2026-22778",
@@ -877,6 +879,7 @@
877
879
  "CVE-2025-48927",
878
880
  "CVE-2025-48928",
879
881
  "CVE-2025-49113",
882
+ "CVE-2025-49596",
880
883
  "CVE-2025-49704",
881
884
  "CVE-2025-49844",
882
885
  "CVE-2025-5086",
@@ -1001,6 +1004,9 @@
1001
1004
  "description": "Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.",
1002
1005
  "tactic": [
1003
1006
  "Initial Access"
1007
+ ],
1008
+ "cve_refs": [
1009
+ "CVE-2025-54136"
1004
1010
  ]
1005
1011
  },
1006
1012
  "T1195.001": {
@@ -9592,6 +9592,219 @@
9592
9592
  "_intake_method": "manual-verified-curation",
9593
9593
  "_kev_short_description": "Microsoft Semantic Kernel SessionsPythonPlugin path traversal enabling arbitrary file write and, via prompt injection, host remote code execution."
9594
9594
  },
9595
+ "CVE-2025-49596": {
9596
+ "name": "MCP Inspector Missing Authentication — Unauthenticated RCE via the Inspector Proxy",
9597
+ "type": "RCE",
9598
+ "cvss_score": 8.3,
9599
+ "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
9600
+ "cvss_note": "Operator v3.1 estimate (NVD has not assessed v3.1; the GitHub CNA published CVSS v4.0 9.4 CRITICAL). Exploitation lures a victim's browser to reach the locally-bound, unauthenticated MCP Inspector proxy (the 0.0.0.0-day / DNS-rebinding class), hence AC:H / UI:R; once reached, commands run over stdio with no auth.",
9601
+ "cisa_kev": false,
9602
+ "poc_available": true,
9603
+ "poc_description": "Publicly documented by Oligo Security (the 0.0.0.0-day / MCP Inspector RCE research): a malicious web page a developer visits can reach the Inspector proxy bound on the loopback/0.0.0.0 and issue unauthenticated requests that launch MCP commands over stdio, yielding RCE on the developer's machine. Technique is fully public; no separate exploit repository required.",
9604
+ "ai_discovered": false,
9605
+ "ai_discovery_source": "human_researcher",
9606
+ "ai_discovery_notes": "Disclosed by Oligo Security via conventional web/SSRF-class research. The affected component is core AI-developer tooling (Anthropic's official MCP Inspector), placing it on the AI/MCP supply-chain surface.",
9607
+ "ai_assisted_weaponization": false,
9608
+ "ai_assisted_notes": "No AI-assisted weaponization; the exploit is a browser-driven cross-origin request chain.",
9609
+ "active_exploitation": "none",
9610
+ "active_exploitation_notes": "Research disclosure with a coordinated fix (0.14.1); no confirmed in-the-wild exploitation reported as of curation. The public technique and the ubiquity of MCP Inspector in agent-developer workflows elevate the watch posture.",
9611
+ "affected": "Anthropic MCP Inspector (the official Model Context Protocol server-testing tool, @modelcontextprotocol/inspector) prior to 0.14.1.",
9612
+ "affected_versions": [
9613
+ "@modelcontextprotocol/inspector < 0.14.1"
9614
+ ],
9615
+ "vector": "The MCP Inspector client and its proxy have no authentication between them, so any unauthenticated request that reaches the proxy can launch MCP commands over stdio — remote code execution on the host running Inspector. Because the proxy is browser-reachable (loopback / 0.0.0.0 binding), a malicious web page a developer visits can drive the requests cross-origin (the 0.0.0.0-day + DNS-rebinding class), with no developer interaction beyond visiting the page.",
9616
+ "complexity": "high",
9617
+ "complexity_notes": "Requires luring the developer's browser to a malicious page and the cross-origin/DNS-rebinding setup (AC:H, UI:R); the missing-auth flaw itself (CWE-306) imposes no further barrier once a request reaches the proxy.",
9618
+ "patch_available": true,
9619
+ "patch_required_reboot": false,
9620
+ "live_patch_available": false,
9621
+ "live_patch_tools": [],
9622
+ "live_patch_notes": "Remediation is a tool upgrade to @modelcontextprotocol/inspector 0.14.1+ (which adds a session-token auth between client and proxy and origin checks); no reboot.",
9623
+ "vendor_update_paths": [
9624
+ "Upgrade @modelcontextprotocol/inspector to 0.14.1 or later (adds proxy auth + origin validation). Until then, do not run MCP Inspector on a machine where a browser may visit untrusted pages, and bind it to loopback only with a firewall."
9625
+ ],
9626
+ "framework_control_gaps": {
9627
+ "NIST-800-53-SI-2": "Flaw-remediation cadence does not track AI-developer tooling (MCP Inspector and similar) as managed, RCE-bearing software on developer workstations.",
9628
+ "ISO-27001-2022-A.8.8": "Vulnerability management rarely enumerates locally-run AI/MCP developer tools as in-scope assets.",
9629
+ "NIS2-Art21-patch-management": "Article 21 measures do not reach developer-workstation AI tooling whose loopback services are browser-reachable.",
9630
+ "DORA-Art-9": "ICT protection measures seldom model a developer's locally-bound MCP tooling as an attacker-reachable RCE surface via the browser.",
9631
+ "UK-CAF-B4": "System Security objective has no objective for hardening locally-bound developer AI services against cross-origin / DNS-rebinding access.",
9632
+ "AU-ISM-1546": "Patch-application control does not single out AI/MCP developer tooling, whose RCE flaws compromise the developer's machine and credentials.",
9633
+ "ALL-AI-PIPELINE-INTEGRITY": "MCP — the connective tissue of the agent ecosystem — concentrates RCE risk in its tooling; no framework treats the MCP toolchain (inspector, proxy, servers) as a supply-chain control plane whose compromise reaches every connected agent and credential."
9634
+ },
9635
+ "atlas_refs": [],
9636
+ "attack_refs": [
9637
+ "T1190",
9638
+ "T1059"
9639
+ ],
9640
+ "rwep_score": 30,
9641
+ "rwep_factors": {
9642
+ "cisa_kev": 0,
9643
+ "poc_available": 20,
9644
+ "ai_factor": 0,
9645
+ "active_exploitation": 0,
9646
+ "blast_radius": 25,
9647
+ "patch_available": -15,
9648
+ "live_patch_available": 0,
9649
+ "reboot_required": 0
9650
+ },
9651
+ "rwep_notes": "P3 (RWEP 30 per lib/scoring.js). Not KEV-listed, no confirmed in-the-wild exploitation, patched at disclosure (Hard Rule #3 — the 9.4 CNA CVSS does not by itself drive priority). poc_available=20 (public Oligo technique) + blast_radius=25 (MCP Inspector is the official, widely-used MCP debug tool) − patch 15. Escalates on observed exploitation; representative of the MCP-toolchain RCE class.",
9652
+ "epss_score": null,
9653
+ "epss_date": "2026-05-25",
9654
+ "epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
9655
+ "epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2025-49596",
9656
+ "cwe_refs": [
9657
+ "CWE-306",
9658
+ "CWE-352",
9659
+ "CWE-346"
9660
+ ],
9661
+ "iocs": {
9662
+ "behavioral": [
9663
+ "The MCP Inspector proxy (default port 6277) receiving requests whose Origin / Referer is an external web page rather than the local Inspector client — the cross-origin driver of the exploit.",
9664
+ "MCP Inspector launching MCP server commands over stdio that were not initiated from the local Inspector UI session.",
9665
+ "An MCP Inspector / Node proxy process spawning unexpected child processes (shell, interpreter) on a developer workstation.",
9666
+ "Deployed @modelcontextprotocol/inspector below 0.14.1 reachable on 0.0.0.0 / loopback while a browser is in use — the exposed precondition."
9667
+ ],
9668
+ "supply_chain_entry_vectors": [
9669
+ "Delivery is a malicious or attacker-controlled web page visited by a developer running MCP Inspector; the developer's browser is the cross-origin entry point, no direct host authentication required."
9670
+ ],
9671
+ "_ioc_source_note": "Behavioral signatures derived from NVD CVE-2025-49596 (CWE-306 missing authentication between Inspector client and proxy enabling stdio command execution) and the Oligo Security primary-source writeup at https://www.oligo.security/blog/critical-rce-vulnerability-in-anthropic-mcp-inspector-cve-2025-49596 (the 0.0.0.0-day / DNS-rebinding MCP Inspector RCE research)."
9672
+ },
9673
+ "source_verified": "2026-05-25",
9674
+ "verification_sources": [
9675
+ "https://nvd.nist.gov/vuln/detail/CVE-2025-49596",
9676
+ "https://www.oligo.security/blog/critical-rce-vulnerability-in-anthropic-mcp-inspector-cve-2025-49596",
9677
+ "https://github.com/modelcontextprotocol/inspector/security/advisories"
9678
+ ],
9679
+ "vendor_advisories": [
9680
+ {
9681
+ "vendor": "GitHub Security Advisory",
9682
+ "advisory_id": "CVE-2025-49596",
9683
+ "url": "https://github.com/modelcontextprotocol/inspector/security/advisories",
9684
+ "severity": "critical",
9685
+ "published_date": "2025-06-13"
9686
+ },
9687
+ {
9688
+ "vendor": "NVD",
9689
+ "advisory_id": "CVE-2025-49596",
9690
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-49596",
9691
+ "severity": "critical",
9692
+ "published_date": "2025-06-13"
9693
+ }
9694
+ ],
9695
+ "last_updated": "2026-05-25",
9696
+ "discovery_attribution_note": "Manually curated from NVD (CWE-306; CNA CVSS v4.0 9.4, v3.1 N/A) + Oligo Security 0.0.0.0-day / MCP Inspector RCE research. Missing authentication between the Inspector client and proxy allows browser-driven, unauthenticated RCE over stdio; fixed in @modelcontextprotocol/inspector 0.14.1. Part of the broader 2026 MCP-toolchain RCE advisory class.",
9697
+ "_auto_imported": false,
9698
+ "_intake_method": "manual-verified-curation",
9699
+ "_kev_short_description": "Anthropic MCP Inspector lacks authentication between its client and proxy, allowing browser-driven unauthenticated remote code execution over stdio."
9700
+ },
9701
+ "CVE-2025-54136": {
9702
+ "name": "Cursor MCPoison — Persistent RCE via Modified Already-Trusted MCP Config",
9703
+ "type": "RCE",
9704
+ "cvss_score": 8.8,
9705
+ "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
9706
+ "cvss_note": "NVD CVSS v3.1 base 8.8 (HIGH). The 'trust-on-first-use, never-re-validated' design lets a one-time approval become silent persistent code execution.",
9707
+ "cisa_kev": false,
9708
+ "poc_available": true,
9709
+ "poc_description": "Check Point Research ('MCPoison') publicly documented the technique: after a user approves an MCP server entry in a project's .cursor/mcp.json, Cursor does not re-validate the config on subsequent edits, so an attacker who later modifies that already-trusted entry (e.g. in a shared / pulled repository) gets their command executed silently each time the project is opened — persistent RCE with no re-prompt.",
9710
+ "ai_discovered": false,
9711
+ "ai_discovery_source": "human_researcher",
9712
+ "ai_discovery_notes": "Disclosed by Check Point Research. The affected component is a leading AI coding IDE (Cursor) and the abused trust boundary is its MCP tool configuration — squarely AI-agent-tool-poisoning territory.",
9713
+ "ai_assisted_weaponization": false,
9714
+ "ai_assisted_notes": "No AI-assisted weaponization; the attack is a configuration-trust bypass.",
9715
+ "active_exploitation": "none",
9716
+ "active_exploitation_notes": "Research disclosure with a coordinated fix (Cursor 1.3); no confirmed in-the-wild exploitation reported as of curation. The shared-repo persistence and Cursor's large install base elevate the watch posture.",
9717
+ "affected": "Cursor (AI code editor) versions 1.2.4 and below; fixed in 1.3.",
9718
+ "affected_versions": [
9719
+ "Cursor <= 1.2.4"
9720
+ ],
9721
+ "vector": "Cursor establishes trust in an MCP server entry when the user first approves it, but does not re-validate the .cursor/mcp.json entry when it is subsequently modified. An attacker who can change that already-trusted entry — by committing to a shared repository the victim pulls, or with local access — substitutes malicious commands (CWE-78 OS command injection via the MCP launch command) that Cursor then executes silently and persistently on every project open. The vulnerability class is AI-agent tool poisoning (ATLAS AML.T0110): a previously-approved tool is mutated into a malicious one with no fresh consent.",
9722
+ "complexity": "low",
9723
+ "complexity_notes": "NVD AC:L / PR:L. Requires the victim to have approved an MCP entry once and the attacker to modify it (shared-repo collaboration or local access); no further interaction is needed thereafter.",
9724
+ "patch_available": true,
9725
+ "patch_required_reboot": false,
9726
+ "live_patch_available": false,
9727
+ "live_patch_tools": [],
9728
+ "live_patch_notes": "Remediation is an application upgrade to Cursor 1.3 or later (which re-validates MCP config changes); no reboot.",
9729
+ "vendor_update_paths": [
9730
+ "Upgrade Cursor to 1.3 or later. Until then, treat .cursor/mcp.json as untrusted in shared repositories, review MCP entries on every pull, and avoid auto-approving MCP servers."
9731
+ ],
9732
+ "framework_control_gaps": {
9733
+ "NIST-800-53-SI-2": "Flaw-remediation cadence does not track the AI IDE / agent tooling on developer workstations as managed, RCE-bearing software.",
9734
+ "ISO-27001-2022-A.8.8": "Vulnerability management rarely enumerates AI coding assistants and their tool-config trust model as in-scope.",
9735
+ "NIS2-Art21-patch-management": "Article 21 measures do not reach the trust-on-first-use model of an AI IDE's MCP configuration.",
9736
+ "DORA-Art-9": "ICT protection measures do not model an approved-once-then-mutated tool config as a persistent code-execution channel.",
9737
+ "UK-CAF-B4": "System Security objective has no objective for re-validating AI-tool configurations after first approval.",
9738
+ "AU-ISM-1546": "Patch-application control does not address the AI-IDE tool-trust class.",
9739
+ "ALL-AI-PIPELINE-INTEGRITY": "No framework treats an AI agent's tool-approval state as a control plane requiring re-validation on change; trust-on-first-use turns a shared-repo config edit into silent persistent RCE across every developer who pulls it."
9740
+ },
9741
+ "atlas_refs": [
9742
+ "AML.T0110",
9743
+ "AML.T0104"
9744
+ ],
9745
+ "attack_refs": [
9746
+ "T1059",
9747
+ "T1195"
9748
+ ],
9749
+ "rwep_score": 30,
9750
+ "rwep_factors": {
9751
+ "cisa_kev": 0,
9752
+ "poc_available": 20,
9753
+ "ai_factor": 0,
9754
+ "active_exploitation": 0,
9755
+ "blast_radius": 25,
9756
+ "patch_available": -15,
9757
+ "live_patch_available": 0,
9758
+ "reboot_required": 0
9759
+ },
9760
+ "rwep_notes": "P3 (RWEP 30 per lib/scoring.js). Not KEV-listed, no confirmed in-the-wild exploitation, patched at disclosure (Hard Rule #3). poc_available=20 (public Check Point technique) + blast_radius=25 (Cursor is a leading AI IDE; shared-repo persistence reaches every developer who pulls) − patch 15. Escalates on observed exploitation; representative of the AI-agent tool-poisoning class.",
9761
+ "epss_score": null,
9762
+ "epss_date": "2026-05-25",
9763
+ "epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
9764
+ "epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2025-54136",
9765
+ "cwe_refs": [
9766
+ "CWE-78",
9767
+ "CWE-829"
9768
+ ],
9769
+ "iocs": {
9770
+ "behavioral": [
9771
+ "A change to a project's .cursor/mcp.json MCP server `command` / `args` between commits or pulls, especially in a shared repository, without a corresponding fresh in-IDE approval prompt.",
9772
+ "Cursor (or its MCP host process) spawning a command from an MCP entry that differs from the command the user originally approved.",
9773
+ "An MCP server entry whose launch command invokes a shell, downloader, or interpreter rather than a legitimate MCP server binary.",
9774
+ "Cursor version 1.2.4 or below in use on a developer machine that opens shared/untrusted repositories — the exposed precondition."
9775
+ ],
9776
+ "supply_chain_entry_vectors": [
9777
+ "Delivery is a modification to an already-approved .cursor/mcp.json in a shared repository (a malicious commit / PR the victim pulls) or via local file access; the trust was established at first approval and never re-checked."
9778
+ ],
9779
+ "_ioc_source_note": "Behavioral signatures derived from NVD CVE-2025-54136 (CWE-78) and Check Point Research's 'MCPoison' disclosure describing persistent RCE via modification of an already-trusted Cursor MCP configuration."
9780
+ },
9781
+ "source_verified": "2026-05-25",
9782
+ "verification_sources": [
9783
+ "https://nvd.nist.gov/vuln/detail/CVE-2025-54136",
9784
+ "https://research.checkpoint.com/2025/cursor-mcpoison-cve-2025-54136/"
9785
+ ],
9786
+ "vendor_advisories": [
9787
+ {
9788
+ "vendor": "Check Point Research",
9789
+ "advisory_id": "CVE-2025-54136",
9790
+ "url": "https://research.checkpoint.com/2025/cursor-mcpoison-cve-2025-54136/",
9791
+ "severity": "high",
9792
+ "published_date": "2025-08-05"
9793
+ },
9794
+ {
9795
+ "vendor": "NVD",
9796
+ "advisory_id": "CVE-2025-54136",
9797
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-54136",
9798
+ "severity": "high",
9799
+ "published_date": "2025-08-05"
9800
+ }
9801
+ ],
9802
+ "last_updated": "2026-05-25",
9803
+ "discovery_attribution_note": "Manually curated from NVD (CWE-78, CVSS 8.8) + Check Point Research 'MCPoison'. Cursor does not re-validate an MCP config entry after first approval, so a later modification of the trusted entry yields persistent silent RCE (ATLAS AML.T0110 AI Agent Tool Poisoning); fixed in Cursor 1.3.",
9804
+ "_auto_imported": false,
9805
+ "_intake_method": "manual-verified-curation",
9806
+ "_kev_short_description": "Cursor does not re-validate a previously-approved MCP configuration entry, so modifying the trusted entry yields persistent silent remote code execution."
9807
+ },
9595
9808
  "CVE-2026-41091": {
9596
9809
  "name": "Microsoft Defender (Malware Protection Engine) Link-Following LPE to SYSTEM",
9597
9810
  "type": "LPE",
@@ -186,6 +186,7 @@
186
186
  "CVE-2025-11953",
187
187
  "CVE-2025-12686",
188
188
  "CVE-2025-48703",
189
+ "CVE-2025-54136",
189
190
  "CVE-2025-54948",
190
191
  "CVE-2025-58034",
191
192
  "CVE-2025-59389",
@@ -707,6 +708,7 @@
707
708
  "CVE-2020-24363",
708
709
  "CVE-2025-32433",
709
710
  "CVE-2025-4008",
711
+ "CVE-2025-49596",
710
712
  "CVE-2025-61757",
711
713
  "CVE-2026-0300",
712
714
  "CVE-2026-24423",
@@ -1036,7 +1038,8 @@
1036
1038
  ],
1037
1039
  "evidence_cves": [
1038
1040
  "CVE-2023-2533",
1039
- "CVE-2025-34291"
1041
+ "CVE-2025-34291",
1042
+ "CVE-2025-49596"
1040
1043
  ],
1041
1044
  "framework_controls_partially_addressing": [
1042
1045
  "NIST-800-53-SC-23",
@@ -1645,6 +1648,7 @@
1645
1648
  ],
1646
1649
  "evidence_cves": [
1647
1650
  "CVE-2025-32463",
1651
+ "CVE-2025-54136",
1648
1652
  "MAL-2026-NODE-IPC-STEALER",
1649
1653
  "MAL-2026-SHAI-HULUD-OSS"
1650
1654
  ],
@@ -2974,7 +2978,8 @@
2974
2978
  ],
2975
2979
  "related_weaknesses": [],
2976
2980
  "evidence_cves": [
2977
- "CVE-2025-34291"
2981
+ "CVE-2025-34291",
2982
+ "CVE-2025-49596"
2978
2983
  ],
2979
2984
  "last_verified": "2026-05-19",
2980
2985
  "notes": "Bulk-imported v0.13.18 from the canonical MITRE Top 25 + commonly-referenced-class expansion.",
@@ -34,7 +34,9 @@
34
34
  "status": "open",
35
35
  "opened_date": "2026-01-01",
36
36
  "evidence_cves": [
37
- "CVE-2025-34291"
37
+ "CVE-2025-34291",
38
+ "CVE-2025-49596",
39
+ "CVE-2025-54136"
38
40
  ],
39
41
  "atlas_refs": [
40
42
  "AML.T0018",
@@ -1433,6 +1435,7 @@
1433
1435
  "CVE-2025-48928",
1434
1436
  "CVE-2025-49113",
1435
1437
  "CVE-2025-4919",
1438
+ "CVE-2025-49596",
1436
1439
  "CVE-2025-49704",
1437
1440
  "CVE-2025-49706",
1438
1441
  "CVE-2025-5086",
@@ -1441,6 +1444,7 @@
1441
1444
  "CVE-2025-53690",
1442
1445
  "CVE-2025-53770",
1443
1446
  "CVE-2025-54068",
1447
+ "CVE-2025-54136",
1444
1448
  "CVE-2025-5419",
1445
1449
  "CVE-2025-54236",
1446
1450
  "CVE-2025-54253",
@@ -1723,6 +1727,8 @@
1723
1727
  "CVE-2025-34291",
1724
1728
  "CVE-2025-38352",
1725
1729
  "CVE-2025-43300",
1730
+ "CVE-2025-49596",
1731
+ "CVE-2025-54136",
1726
1732
  "CVE-2026-25592",
1727
1733
  "CVE-2026-31431",
1728
1734
  "CVE-2026-34926",
@@ -2361,6 +2367,7 @@
2361
2367
  "CVE-2025-48928",
2362
2368
  "CVE-2025-49113",
2363
2369
  "CVE-2025-4919",
2370
+ "CVE-2025-49596",
2364
2371
  "CVE-2025-49704",
2365
2372
  "CVE-2025-49706",
2366
2373
  "CVE-2025-5086",
@@ -2369,6 +2376,7 @@
2369
2376
  "CVE-2025-53690",
2370
2377
  "CVE-2025-53770",
2371
2378
  "CVE-2025-54068",
2379
+ "CVE-2025-54136",
2372
2380
  "CVE-2025-5419",
2373
2381
  "CVE-2025-54236",
2374
2382
  "CVE-2025-54253",
@@ -4713,6 +4721,8 @@
4713
4721
  "evidence_cves": [
4714
4722
  "CVE-2024-21762",
4715
4723
  "CVE-2025-34291",
4724
+ "CVE-2025-49596",
4725
+ "CVE-2025-54136",
4716
4726
  "CVE-2026-0300",
4717
4727
  "CVE-2026-20182",
4718
4728
  "CVE-2026-25592",
@@ -5210,6 +5220,8 @@
5210
5220
  "evidence_cves": [
5211
5221
  "CVE-2024-21762",
5212
5222
  "CVE-2025-34291",
5223
+ "CVE-2025-49596",
5224
+ "CVE-2025-54136",
5213
5225
  "CVE-2026-25592",
5214
5226
  "CVE-2026-34926",
5215
5227
  "CVE-2026-41091",
@@ -5249,6 +5261,8 @@
5249
5261
  "evidence_cves": [
5250
5262
  "CVE-2024-21762",
5251
5263
  "CVE-2025-34291",
5264
+ "CVE-2025-49596",
5265
+ "CVE-2025-54136",
5252
5266
  "CVE-2026-25592",
5253
5267
  "CVE-2026-34926",
5254
5268
  "CVE-2026-41091",
@@ -5983,6 +5983,106 @@
5983
5983
  "_auto_imported": false,
5984
5984
  "_intake_method": "manual-verified-curation"
5985
5985
  },
5986
+ "CVE-2025-49596": {
5987
+ "name": "MCP Inspector Missing Authentication — Unauthenticated RCE via the Inspector Proxy",
5988
+ "lesson_date": "2026-05-25",
5989
+ "attack_vector": {
5990
+ "description": "Anthropic's official MCP Inspector has no authentication between its client and proxy; because the proxy is browser-reachable (loopback / 0.0.0.0), a malicious web page a developer visits can issue unauthenticated cross-origin requests that launch MCP commands over stdio — RCE on the developer's machine (the 0.0.0.0-day / DNS-rebinding class).",
5991
+ "privileges_required": "none on the host — the developer need only run MCP Inspector and visit an attacker-controlled web page",
5992
+ "complexity": "high (browser lure + cross-origin/DNS-rebinding setup), but the missing-auth flaw itself imposes no barrier once a request reaches the proxy",
5993
+ "ai_factor": "The compromised component is core AI/MCP developer tooling. The lesson: MCP — the connective tissue of the agent ecosystem — concentrates RCE risk in its toolchain (inspector, proxy, servers); locally-bound AI dev services are browser-reachable and must authenticate and origin-validate. Surfaced via the MCP supply-chain advisory + GHSA feeds."
5994
+ },
5995
+ "framework_coverage": {
5996
+ "NIST-800-53-SI-2": {
5997
+ "covered": true,
5998
+ "adequate": false,
5999
+ "gap": "Flaw-remediation cadence does not track AI/MCP developer tooling on workstations as managed, RCE-bearing software."
6000
+ },
6001
+ "ISO-27001-2022-A.8.8": {
6002
+ "covered": true,
6003
+ "adequate": false,
6004
+ "gap": "Vulnerability management rarely enumerates locally-run AI/MCP developer tools as in-scope assets."
6005
+ },
6006
+ "ALL-AI-PIPELINE-INTEGRITY": {
6007
+ "covered": false,
6008
+ "adequate": false,
6009
+ "gap": "No framework treats the MCP toolchain as a supply-chain control plane whose compromise reaches every connected agent and credential."
6010
+ }
6011
+ },
6012
+ "compliance_exposure_score": {
6013
+ "percent_audit_passing_orgs_still_exposed": 70,
6014
+ "basis": "Developer-workstation AI/MCP tooling is almost never in the managed vulnerability program; loopback services are assumed unreachable, ignoring browser-driven cross-origin / DNS-rebinding access.",
6015
+ "theater_pattern": "ai_supply_chain_trust"
6016
+ },
6017
+ "ai_discovered_zeroday": false,
6018
+ "ai_discovery_source": "human_researcher",
6019
+ "ai_assist_factor": "none",
6020
+ "new_control_requirements": [
6021
+ {
6022
+ "id": "NEW-CTRL-081",
6023
+ "name": "MCP-TOOLCHAIN-LOCALHOST-AUTH",
6024
+ "description": "Locally-bound AI/MCP developer services (Inspector, proxies, dev servers) must authenticate their own client↔service channel and validate request Origin, never trusting loopback / 0.0.0.0 reachability as an access-control boundary (browsers can reach it cross-origin via the 0.0.0.0-day and DNS rebinding). Track MCP toolchain packages (e.g. @modelcontextprotocol/inspector >= 0.14.1) as managed, patch-prioritized software on developer workstations.",
6025
+ "evidence": "https://nvd.nist.gov/vuln/detail/CVE-2025-49596",
6026
+ "gap_closes": [
6027
+ "NIST-800-53-SI-2",
6028
+ "ISO-27001-2022-A.8.8",
6029
+ "ALL-AI-PIPELINE-INTEGRITY"
6030
+ ]
6031
+ }
6032
+ ],
6033
+ "_auto_imported": false,
6034
+ "_intake_method": "manual-verified-curation"
6035
+ },
6036
+ "CVE-2025-54136": {
6037
+ "name": "Cursor MCPoison — Persistent RCE via Modified Already-Trusted MCP Config",
6038
+ "lesson_date": "2026-05-25",
6039
+ "attack_vector": {
6040
+ "description": "Cursor trusts an MCP server entry when the user first approves it but never re-validates the .cursor/mcp.json entry on later edits. An attacker who modifies that already-trusted entry (via a shared repo the victim pulls, or local access) substitutes malicious commands (CWE-78) that Cursor runs silently and persistently on every project open — AI-agent tool poisoning (ATLAS AML.T0110).",
6041
+ "privileges_required": "low — the victim must have approved an MCP entry once; the attacker then modifies it (shared-repo collaboration or local access)",
6042
+ "complexity": "low (NVD AC:L); no re-prompt after the first approval",
6043
+ "ai_factor": "The trust boundary is an AI IDE's MCP tool configuration. The lesson: an AI agent's tool-approval is not a one-time decision — the approved artifact can be mutated, so tool configs must be re-validated on change. Surfaced via Check Point Research + GHSA/MCP advisory feeds."
6044
+ },
6045
+ "framework_coverage": {
6046
+ "NIST-800-53-SI-2": {
6047
+ "covered": true,
6048
+ "adequate": false,
6049
+ "gap": "Does not track AI IDE / agent tooling on workstations as managed, RCE-bearing software."
6050
+ },
6051
+ "ISO-27001-2022-A.8.8": {
6052
+ "covered": true,
6053
+ "adequate": false,
6054
+ "gap": "Does not enumerate AI coding assistants and their tool-config trust model as in-scope."
6055
+ },
6056
+ "ALL-AI-PIPELINE-INTEGRITY": {
6057
+ "covered": false,
6058
+ "adequate": false,
6059
+ "gap": "No framework treats an AI agent's tool-approval state as a control plane requiring re-validation on change; trust-on-first-use turns a shared-repo config edit into silent persistent RCE."
6060
+ }
6061
+ },
6062
+ "compliance_exposure_score": {
6063
+ "percent_audit_passing_orgs_still_exposed": 70,
6064
+ "basis": "Developer AI IDEs and their MCP tool configs are almost never in the managed vulnerability program, and tool-approval trust is treated as a one-time event; shared-repo config edits are not reviewed as code-execution changes.",
6065
+ "theater_pattern": "ai_supply_chain_trust"
6066
+ },
6067
+ "ai_discovered_zeroday": false,
6068
+ "ai_discovery_source": "human_researcher",
6069
+ "ai_assist_factor": "none",
6070
+ "new_control_requirements": [
6071
+ {
6072
+ "id": "NEW-CTRL-082",
6073
+ "name": "AI-AGENT-TOOL-APPROVAL-REVALIDATION",
6074
+ "description": "An AI agent / IDE must re-validate a tool configuration (MCP server entry, plugin command) whenever its definition changes, not trust it indefinitely after first approval. Treat tool-config files (e.g. .cursor/mcp.json) as untrusted in shared repositories, diff and re-approve MCP entries on every change, disable auto-approval of tool servers, and track the AI IDE itself (e.g. Cursor >= 1.3) as managed, patch-prioritized software.",
6075
+ "evidence": "https://research.checkpoint.com/2025/cursor-mcpoison-cve-2025-54136/",
6076
+ "gap_closes": [
6077
+ "NIST-800-53-SI-2",
6078
+ "ISO-27001-2022-A.8.8",
6079
+ "ALL-AI-PIPELINE-INTEGRITY"
6080
+ ]
6081
+ }
6082
+ ],
6083
+ "_auto_imported": false,
6084
+ "_intake_method": "manual-verified-curation"
6085
+ },
5986
6086
  "CVE-2025-34291": {
5987
6087
  "name": "Langflow Account Takeover + RCE (CORS / refresh-token chain)",
5988
6088
  "lesson_date": "2026-05-24",