@blamejs/exceptd-skills 0.13.102 → 0.13.104

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.
@@ -9253,104 +9253,6 @@
9253
9253
  "_intake_method": "v0.13.17-bulk-cisa-kev-import",
9254
9254
  "_kev_short_description": "Aquasecurity Trivy contains an embedded malicious code vulnerability that could allow an attacker to gain access to everything in the CI/CD environment, including all tokens, SSH keys, cloud credentials, database passwords, and any sensitive configuration in memory."
9255
9255
  },
9256
- "CVE-2026-33017": {
9257
- "name": "Langflow Code Injection Vulnerability",
9258
- "type": "RCE",
9259
- "cvss_score": 9.8,
9260
- "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
9261
- "cvss_note": "Operator estimate inferred from KEV vulnerabilityName + shortDescription classification (no per-CVE NVD lookup at bulk-import time). Refine via `exceptd refresh --advisory <CVE-ID> --apply` for NVD/GHSA/OSV enrichment.",
9262
- "cisa_kev": true,
9263
- "cisa_kev_date": "2026-03-25",
9264
- "cisa_kev_due_date": "2026-04-08",
9265
- "poc_available": true,
9266
- "poc_description": "KEV-listed actively-exploited vulnerability. CISA listing 2026-05 catalog version. Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable..",
9267
- "ai_discovered": false,
9268
- "ai_discovery_source": "unknown",
9269
- "ai_discovery_notes": "Bulk-imported KEV entry — AI-discovery provenance not surfaced in the KEV record. Refine via NVD/GHSA enrichment if researcher attribution names an AI tool.",
9270
- "ai_assisted_weaponization": false,
9271
- "ai_assisted_notes": "Bulk-imported KEV entry — weaponization-channel attribution not in KEV.",
9272
- "active_exploitation": "confirmed",
9273
- "active_exploitation_notes": "KEV listing is CISA's confirmed-exploitation attestation. The dateAdded is the formal KEV listing date; the actual in-wild observation may predate it by weeks.",
9274
- "affected": "Langflow Langflow — see vendor advisory linked in verification_sources for affected version ranges.",
9275
- "affected_versions": [
9276
- "Langflow Langflow — versions per vendor advisory"
9277
- ],
9278
- "vector": "Langflow contains a code injection vulnerability that could allow building public flows without requiring authentication.",
9279
- "complexity": "moderate",
9280
- "complexity_notes": "Bulk-imported — exploitation complexity not extracted from KEV record. Treat as moderate-by-default; refine when researcher writeup published.",
9281
- "patch_available": true,
9282
- "patch_required_reboot": true,
9283
- "live_patch_available": false,
9284
- "live_patch_tools": [],
9285
- "live_patch_notes": "No live-patch tool registered for this entry at bulk-import time. Vendor patch typically requires service restart or system reboot per the KEV requiredAction.",
9286
- "vendor_update_paths": [
9287
- "Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable."
9288
- ],
9289
- "framework_control_gaps": {
9290
- "NIST-800-53-SI-2": "30-day flaw-remediation SLA inadequate for CISA-KEV-listed actively-exploited CVE. CISA due date is the operationally-meaningful clock — typically 14-21 days for new KEV listings.",
9291
- "ISO-27001-2022-A.8.8": "Vulnerability management standard does not differentiate between routinely-disclosed CVEs and actively-exploited KEV-listed CVEs. KEV listing collapses 'patch-cycle response' to 'incident-speed response'.",
9292
- "NIST-800-53-AC-6": "Least-privilege presumes a working authentication / authorization boundary. The KEV-listed exploit demonstrates the boundary is breakable from a baseline context."
9293
- },
9294
- "atlas_refs": [],
9295
- "attack_refs": [
9296
- "T1190"
9297
- ],
9298
- "rwep_score": 77,
9299
- "rwep_factors": {
9300
- "cisa_kev": 25,
9301
- "poc_available": 20,
9302
- "ai_factor": 0,
9303
- "active_exploitation": 20,
9304
- "blast_radius": 22,
9305
- "patch_available": -15,
9306
- "live_patch_available": 0,
9307
- "reboot_required": 5
9308
- },
9309
- "rwep_notes": "P1 — KEV-listed confirmed exploitation. blast_radius=22 (standard vendor-product scope). Bulk-imported via v0.13.17 KEV intake — score reflects KEV+PoC+active_exploitation contributions; refine factors when per-CVE research publishes.",
9310
- "epss_score": null,
9311
- "epss_date": "2026-05-18",
9312
- "epss_note": "EPSS not refreshed at bulk-import. Pull via FIRST EPSS API per-CVE in a future refresh.",
9313
- "epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2026-33017",
9314
- "cwe_refs": [
9315
- "CWE-94",
9316
- "CWE-95",
9317
- "CWE-306"
9318
- ],
9319
- "source_verified": "2026-05-18",
9320
- "verification_sources": [
9321
- "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
9322
- "https://github.com/langflow-ai/langflow/security/advisories/GHSA-vwmf-pq79-vjvx",
9323
- "https://nvd.nist.gov/vuln/detail/CVE-2026-33017"
9324
- ],
9325
- "vendor_advisories": [
9326
- {
9327
- "vendor": "CISA KEV",
9328
- "advisory_id": "CVE-2026-33017",
9329
- "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
9330
- "severity": "high",
9331
- "published_date": "2026-03-25"
9332
- },
9333
- {
9334
- "vendor": "Langflow",
9335
- "advisory_id": null,
9336
- "url": "https://github.com/langflow-ai/langflow/security/advisories/GHSA-vwmf-pq79-vjvx",
9337
- "severity": "high",
9338
- "published_date": "2026-03-25"
9339
- },
9340
- {
9341
- "vendor": "Langflow",
9342
- "advisory_id": null,
9343
- "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33017",
9344
- "severity": "high",
9345
- "published_date": "2026-03-25"
9346
- }
9347
- ],
9348
- "last_updated": "2026-05-18",
9349
- "discovery_attribution_note": "Bulk-imported from CISA KEV catalog version 2026.05.15. KEV listing date 2026-03-25; due date 2026-04-08. Notes reference: https://github.com/langflow-ai/langflow/security/advisories/GHSA-vwmf-pq79-vjvx ; https://nvd.nist.gov/vuln/detail/CVE-2026-33017",
9350
- "_auto_imported": true,
9351
- "_intake_method": "v0.13.17-bulk-cisa-kev-import",
9352
- "_kev_short_description": "Langflow contains a code injection vulnerability that could allow building public flows without requiring authentication."
9353
- },
9354
9256
  "CVE-2025-34291": {
9355
9257
  "name": "Langflow Account Takeover + RCE (CORS / refresh-token chain)",
9356
9258
  "type": "RCE",
@@ -15913,6 +15815,444 @@
15913
15815
  "_intake_method": "manual-verified-curation",
15914
15816
  "_kev_short_description": "PandasAI chat natural-language interface runs LLM-generated Python without separating malicious input, so prompt injection yields unauthenticated RCE / sandbox escape (CWE-94); no fixed release - enable the security agent + sandbox."
15915
15817
  },
15818
+ "CVE-2025-3248": {
15819
+ "name": "Langflow /api/v1/validate/code Unauthenticated Code Injection (CISA KEV)",
15820
+ "type": "RCE",
15821
+ "cvss_score": 9.8,
15822
+ "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
15823
+ "cvss_note": "VulnCheck (CNA) CVSS v3.1 base 9.8 (CRITICAL). The /api/v1/validate/code endpoint compiles and runs attacker-supplied Python with no authentication, so a crafted HTTP request runs arbitrary code on the host (CWE-94 + CWE-306).",
15824
+ "cisa_kev": true,
15825
+ "cisa_kev_date": "2025-05-05",
15826
+ "cisa_kev_due_date": "2025-05-26",
15827
+ "poc_available": true,
15828
+ "poc_description": "VulnCheck published a working proof-of-concept and analysis; exploitation is a single unauthenticated POST to /api/v1/validate/code.",
15829
+ "ai_discovered": false,
15830
+ "ai_discovery_source": "human_researcher",
15831
+ "ai_discovery_notes": "Disclosed via GitHub Security Advisory (https://github.com/advisories/GHSA-rvqx-wpfh-mfx7). The abused surface is a widely used visual LLM app/agent builder (Langflow).",
15832
+ "ai_assisted_weaponization": false,
15833
+ "ai_assisted_notes": "No AI-assisted weaponization; an unauthenticated endpoint on an LLM app builder reaches a code-execution sink.",
15834
+ "active_exploitation": "confirmed",
15835
+ "active_exploitation_notes": "CISA added CVE-2025-3248 to the Known Exploited Vulnerabilities catalog on 2025-05-05 (due 2025-05-26) - confirmed active exploitation. Mass scanning and botnet activity against internet-exposed Langflow instances was reported following VulnCheck's public proof-of-concept; Sysdig documented an end-to-end compromise of an exposed Langflow instance within hours.",
15836
+ "affected": "Langflow before 1.3.0.",
15837
+ "affected_versions": [
15838
+ "Langflow < 1.3.0"
15839
+ ],
15840
+ "vector": "Langflow is a popular visual builder for LLM agents and flows. Before 1.3.0 its /api/v1/validate/code endpoint accepts code in an HTTP request and runs it through a Python compile-and-run path to 'validate' it, but the endpoint requires no authentication - so any remote attacker who can reach the server runs arbitrary code (CWE-94 code injection + CWE-306 missing authentication). VulnCheck published the analysis and PoC; CISA KEV-listed it.",
15841
+ "complexity": "low",
15842
+ "complexity_notes": "AV:N / AC:L / PR:N / UI:N - network-reachable, unauthenticated, no user interaction; a single crafted request to the validate-code endpoint runs code.",
15843
+ "patch_available": true,
15844
+ "patch_required_reboot": false,
15845
+ "live_patch_available": false,
15846
+ "live_patch_tools": [],
15847
+ "live_patch_notes": "Remediation is upgrading to 1.3.0 or later; redeploy, no host reboot.",
15848
+ "vendor_update_paths": [
15849
+ "Upgrade Langflow to the latest release (1.3.0 closed this route; 1.9.0+ closes the sibling flow-build route in CVE-2026-33017). Do not expose Langflow to untrusted networks, place it behind authenticated reverse-proxy access control, and treat every flow validate/build/run endpoint as a code-execution surface."
15850
+ ],
15851
+ "framework_control_gaps": {
15852
+ "NIST-800-53-AC-3": "Access enforcement is missing on a code-execution endpoint - the flow validate/build path is reachable without authentication (CWE-306).",
15853
+ "NIST-800-53-IA-2": "The LLM app builder does not authenticate callers before reaching a code-execution endpoint.",
15854
+ "NIST-800-53-SI-3": "Malicious-code protection does not treat the app builder's code validate/build endpoint as an attacker-reachable execution channel.",
15855
+ "NIST-800-53-CM-7": "Least-functionality is not enforced: a public endpoint runs flow-supplied / submitted code through a compile-and-run path without sandboxing.",
15856
+ "ISO-27001-2022-A.5.15": "Access control does not gate the LLM app builder's code-execution endpoints.",
15857
+ "ISO-27001-2022-A.8.28": "Secure-coding expectations do not address running externally supplied code through a dynamic-execution sink on a public endpoint.",
15858
+ "NIS2-Art21-identity-management": "Article 21 access-control measures do not reach the LLM app builder's unauthenticated execution endpoints.",
15859
+ "DORA-Art-9": "ICT protection measures do not model an LLM app builder's public code endpoint as an ICT-risk event.",
15860
+ "UK-CAF-B4": "System Security objective has no objective for authenticating and sandboxing LLM app-builder execution endpoints.",
15861
+ "AU-ISM-1546": "Patch-application control does not single out LLM app builders.",
15862
+ "ALL-AI-PIPELINE-INTEGRITY": "No framework treats a visual LLM app/agent builder's flow validate/build endpoints as privileged execution surfaces that must authenticate and sandbox submitted code."
15863
+ },
15864
+ "atlas_refs": [
15865
+ "AML.T0049"
15866
+ ],
15867
+ "attack_refs": [
15868
+ "T1190",
15869
+ "T1059",
15870
+ "T1059.006"
15871
+ ],
15872
+ "rwep_score": 78,
15873
+ "rwep_factors": {
15874
+ "cisa_kev": 25,
15875
+ "poc_available": 20,
15876
+ "ai_factor": 0,
15877
+ "active_exploitation": 20,
15878
+ "blast_radius": 28,
15879
+ "patch_available": -15,
15880
+ "live_patch_available": 0,
15881
+ "reboot_required": 0
15882
+ },
15883
+ "rwep_notes": "Critical (RWEP 78, \"patch within 24 hours\" band per lib/scoring.js timeline). CISA KEV-listed (added 2025-05-05) and actively exploited: cisa_kev=25 + active_exploitation(confirmed)=20 + poc_available=20 + blast_radius=28, minus patch_available 15. The patch credit does not pull it out of the P1 band because real-world exploitation is confirmed. This is the first of two Langflow flow-execution endpoints KEV-listed for the same unauthenticated code-injection class - its sibling CVE-2026-33017 (the public flow-build endpoint, KEV 2026-03-25) also scores P1, which is the lesson: the first fix closed one route but not the class.",
15884
+ "epss_score": null,
15885
+ "epss_date": "2026-05-25",
15886
+ "epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
15887
+ "epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2025-3248",
15888
+ "cwe_refs": [
15889
+ "CWE-94",
15890
+ "CWE-306"
15891
+ ],
15892
+ "iocs": {
15893
+ "behavioral": [
15894
+ "Unauthenticated POST requests to /api/v1/validate/code carrying Python payloads (decorators, imports, or default-argument tricks that run at compile time).",
15895
+ "Langflow process spawning shell, network, or file-system child processes from the code-validation path.",
15896
+ "Internet-exposed Langflow ( /api/v1/validate/code reachable without auth) being scanned or hit by known PoC payloads."
15897
+ ],
15898
+ "_ioc_source_note": "Behavioral signatures anchored to the GitHub Security Advisory advisory (https://github.com/advisories/GHSA-rvqx-wpfh-mfx7), VulnCheck's research (https://www.vulncheck.com/blog/langflow-rce), the CISA KEV listing, and CWE-94/CWE-306."
15899
+ },
15900
+ "source_verified": "2026-05-25",
15901
+ "verification_sources": [
15902
+ "https://nvd.nist.gov/vuln/detail/CVE-2025-3248",
15903
+ "https://github.com/advisories/GHSA-rvqx-wpfh-mfx7",
15904
+ "https://www.vulncheck.com/blog/langflow-rce",
15905
+ "https://www.cisa.gov/known-exploited-vulnerabilities-catalog"
15906
+ ],
15907
+ "vendor_advisories": [
15908
+ {
15909
+ "vendor": "GitHub Security Advisory",
15910
+ "advisory_id": "CVE-2025-3248",
15911
+ "url": "https://github.com/advisories/GHSA-rvqx-wpfh-mfx7",
15912
+ "severity": "critical",
15913
+ "published_date": "2025-06-17"
15914
+ },
15915
+ {
15916
+ "vendor": "NVD",
15917
+ "advisory_id": "CVE-2025-3248",
15918
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-3248",
15919
+ "severity": "critical",
15920
+ "published_date": "2025-06-17"
15921
+ }
15922
+ ],
15923
+ "last_updated": "2026-05-25",
15924
+ "discovery_attribution_note": "Manually curated from the GitHub Security Advisory advisory (https://github.com/advisories/GHSA-rvqx-wpfh-mfx7, CWE-94/CWE-306) + NVD + VulnCheck (CNA, CVSS v3.1 9.8) + the CISA KEV listing (added 2025-05-05). Visual LLM app/agent-builder flaw (Langflow); shares the app-builder execution-endpoint control NEW-CTRL-103.",
15925
+ "_auto_imported": false,
15926
+ "_intake_method": "manual-verified-curation",
15927
+ "_kev_short_description": "Langflow's /api/v1/validate/code endpoint runs attacker-supplied Python with no authentication (CWE-94/CWE-306), giving unauthenticated RCE; CISA KEV (added 2025-05-05, actively exploited), fixed in 1.3.0."
15928
+ },
15929
+ "CVE-2026-33017": {
15930
+ "name": "Langflow Public Flow-Build Endpoint Unauthenticated Remote Code Execution (CISA KEV)",
15931
+ "type": "RCE",
15932
+ "cvss_score": 9.8,
15933
+ "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
15934
+ "cvss_note": "NIST (NVD) CVSS v3.1 base 9.8 (CRITICAL); the GitHub (CNA) advisory rates it CVSS v4.0 9.3 (CRITICAL). The unauthenticated POST /api/v1/build_public_tmp/{flow_id}/flow endpoint accepts attacker-controlled flow data containing Python that runs through an unsandboxed dynamic-execution sink (CWE-94 / CWE-95 / CWE-306).",
15935
+ "cisa_kev": true,
15936
+ "cisa_kev_date": "2026-03-25",
15937
+ "cisa_kev_due_date": "2026-04-08",
15938
+ "poc_available": true,
15939
+ "poc_description": "The advisory ships a full proof-of-concept: obtain a public flow id via AUTO_LOGIN, then POST attacker-controlled flow data with embedded Python to /api/v1/build_public_tmp/{flow_id}/flow; the advisory documents a confirmed end-to-end RCE.",
15940
+ "ai_discovered": false,
15941
+ "ai_discovery_source": "human_researcher",
15942
+ "ai_discovery_notes": "Disclosed via GitHub Security Advisory (https://github.com/advisories/GHSA-vwmf-pq79-vjvx). The abused surface is a widely used visual LLM app/agent builder (Langflow).",
15943
+ "ai_assisted_weaponization": false,
15944
+ "ai_assisted_notes": "No AI-assisted weaponization; an unauthenticated endpoint on an LLM app builder reaches a code-execution sink.",
15945
+ "active_exploitation": "confirmed",
15946
+ "active_exploitation_notes": "CISA added CVE-2026-33017 to the Known Exploited Vulnerabilities catalog on 2026-03-25 (due 2026-04-08) - confirmed active exploitation. This is the SECOND Langflow flow-execution endpoint to be KEV-listed: the CVE-2025-3248 fix (1.3.0) closed /api/v1/validate/code, but the public flow-build route remained an unauthenticated code-execution path and was itself exploited in the wild. A full proof-of-concept ships in the advisory.",
15947
+ "affected": "Langflow through 1.8.2.",
15948
+ "affected_versions": [
15949
+ "Langflow <= 1.8.2"
15950
+ ],
15951
+ "vector": "After the CVE-2025-3248 fix, Langflow's public flow execution surface remained exploitable through a different route: the unauthenticated POST /api/v1/build_public_tmp/{flow_id}/flow endpoint accepts attacker-controlled flow definitions whose embedded Python runs through an unsandboxed dynamic-execution sink. A remote unauthenticated attacker reaches code execution again - the same code-injection class recurring on a new endpoint, and CISA KEV-listed a second time. Fixed in 1.9.0.",
15952
+ "complexity": "low",
15953
+ "complexity_notes": "NVD AV:N / AC:L / PR:N / UI:N - the public flow-build endpoint is reachable unauthenticated and runs flow-supplied code.",
15954
+ "patch_available": true,
15955
+ "patch_required_reboot": false,
15956
+ "live_patch_available": false,
15957
+ "live_patch_tools": [],
15958
+ "live_patch_notes": "Remediation is upgrading to 1.9.0 or later; redeploy, no host reboot.",
15959
+ "vendor_update_paths": [
15960
+ "Upgrade Langflow to 1.9.0 or later. Do not expose Langflow to untrusted networks; every public flow-build/validate/run endpoint must authenticate and must not run flow-supplied code unsandboxed - the 1.3.0 fix for CVE-2025-3248 did not cover this route."
15961
+ ],
15962
+ "framework_control_gaps": {
15963
+ "NIST-800-53-AC-3": "Access enforcement is missing on a code-execution endpoint - the flow validate/build path is reachable without authentication (CWE-306).",
15964
+ "NIST-800-53-IA-2": "The LLM app builder does not authenticate callers before reaching a code-execution endpoint.",
15965
+ "NIST-800-53-SI-3": "Malicious-code protection does not treat the app builder's code validate/build endpoint as an attacker-reachable execution channel.",
15966
+ "NIST-800-53-CM-7": "Least-functionality is not enforced: a public endpoint runs flow-supplied / submitted code through a compile-and-run path without sandboxing.",
15967
+ "ISO-27001-2022-A.5.15": "Access control does not gate the LLM app builder's code-execution endpoints.",
15968
+ "ISO-27001-2022-A.8.28": "Secure-coding expectations do not address running externally supplied code through a dynamic-execution sink on a public endpoint.",
15969
+ "NIS2-Art21-identity-management": "Article 21 access-control measures do not reach the LLM app builder's unauthenticated execution endpoints.",
15970
+ "DORA-Art-9": "ICT protection measures do not model an LLM app builder's public code endpoint as an ICT-risk event.",
15971
+ "UK-CAF-B4": "System Security objective has no objective for authenticating and sandboxing LLM app-builder execution endpoints.",
15972
+ "AU-ISM-1546": "Patch-application control does not single out LLM app builders.",
15973
+ "ALL-AI-PIPELINE-INTEGRITY": "No framework treats a visual LLM app/agent builder's flow validate/build endpoints as privileged execution surfaces that must authenticate and sandbox submitted code."
15974
+ },
15975
+ "atlas_refs": [
15976
+ "AML.T0049"
15977
+ ],
15978
+ "attack_refs": [
15979
+ "T1190",
15980
+ "T1059",
15981
+ "T1059.006"
15982
+ ],
15983
+ "rwep_score": 78,
15984
+ "rwep_factors": {
15985
+ "cisa_kev": 25,
15986
+ "poc_available": 20,
15987
+ "ai_factor": 0,
15988
+ "active_exploitation": 20,
15989
+ "blast_radius": 28,
15990
+ "patch_available": -15,
15991
+ "live_patch_available": 0,
15992
+ "reboot_required": 0
15993
+ },
15994
+ "rwep_notes": "Critical (RWEP 78, \"patch within 24 hours\" band per lib/scoring.js timeline). CISA KEV-listed (added 2026-03-25) and actively exploited: cisa_kev=25 + active_exploitation(confirmed)=20 + poc_available=20 + blast_radius=28, minus patch_available 15. The patch credit does not pull it out of the P1 band because real-world exploitation is confirmed. This is the second of two Langflow flow-execution endpoints KEV-listed for the same unauthenticated code-injection class - its sibling CVE-2025-3248 (the /api/v1/validate/code endpoint, KEV 2025-05-05) also scores P1, which is the lesson: the first fix closed one route but not the class.",
15995
+ "epss_score": null,
15996
+ "epss_date": "2026-05-25",
15997
+ "epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
15998
+ "epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2026-33017",
15999
+ "cwe_refs": [
16000
+ "CWE-94",
16001
+ "CWE-95",
16002
+ "CWE-306"
16003
+ ],
16004
+ "iocs": {
16005
+ "behavioral": [
16006
+ "Unauthenticated POST requests to /api/v1/build_public_tmp/{flow_id}/flow carrying flow definitions with embedded Python / dynamic-evaluation payloads.",
16007
+ "Langflow running flow-supplied Python that performs file, network, or process operations.",
16008
+ "Langflow <= 1.8.2 with the public flow-build endpoint reachable without authentication - the exposed precondition."
16009
+ ],
16010
+ "_ioc_source_note": "Behavioral signatures anchored to the GitHub Security Advisory advisory (https://github.com/advisories/GHSA-vwmf-pq79-vjvx), NVD CVE-2026-33017 (https://nvd.nist.gov/vuln/detail/CVE-2026-33017), the CISA KEV listing, and CWE-94/CWE-95/CWE-306."
16011
+ },
16012
+ "source_verified": "2026-05-25",
16013
+ "verification_sources": [
16014
+ "https://nvd.nist.gov/vuln/detail/CVE-2026-33017",
16015
+ "https://github.com/advisories/GHSA-vwmf-pq79-vjvx",
16016
+ "https://nvd.nist.gov/vuln/detail/CVE-2026-33017",
16017
+ "https://www.cisa.gov/known-exploited-vulnerabilities-catalog"
16018
+ ],
16019
+ "vendor_advisories": [
16020
+ {
16021
+ "vendor": "GitHub Security Advisory",
16022
+ "advisory_id": "CVE-2026-33017",
16023
+ "url": "https://github.com/advisories/GHSA-vwmf-pq79-vjvx",
16024
+ "severity": "critical",
16025
+ "published_date": "2026-03-17"
16026
+ },
16027
+ {
16028
+ "vendor": "NVD",
16029
+ "advisory_id": "CVE-2026-33017",
16030
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33017",
16031
+ "severity": "critical",
16032
+ "published_date": "2026-03-17"
16033
+ }
16034
+ ],
16035
+ "last_updated": "2026-05-25",
16036
+ "discovery_attribution_note": "Manually curated from the GitHub Security Advisory advisory (https://github.com/advisories/GHSA-vwmf-pq79-vjvx, CWE-94/CWE-95/CWE-306) + NVD (CVSS v3.1 9.8; GitHub CNA CVSS v4.0 9.3) + the CISA KEV listing (added 2026-03-25). Visual LLM app/agent-builder flaw (Langflow); shares the app-builder execution-endpoint control NEW-CTRL-103.",
16037
+ "_auto_imported": false,
16038
+ "_intake_method": "manual-verified-curation",
16039
+ "_kev_short_description": "Langflow's unauthenticated public flow-build endpoint runs flow-supplied Python through an unsandboxed dynamic-execution sink (CWE-94/CWE-95/CWE-306), giving unauthenticated RCE; CISA KEV (added 2026-03-25, actively exploited), fixed in 1.9.0."
16040
+ },
16041
+ "CVE-2024-24590": {
16042
+ "name": "ClearML Client SDK Artifact Deserialization Remote Code Execution",
16043
+ "type": "RCE",
16044
+ "cvss_score": 8.8,
16045
+ "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
16046
+ "cvss_note": "NIST (NVD) CVSS v3.1 base 8.8 (HIGH); HiddenLayer (CNA) rates it 8.0 (HIGH, PR:L). The ClearML client SDK deserializes a stored artifact through an unsafe Python object-deserialization path when a user retrieves it, so a maliciously uploaded artifact runs arbitrary code on the retrieving user's system (CWE-502).",
16047
+ "cisa_kev": false,
16048
+ "poc_available": true,
16049
+ "poc_description": "HiddenLayer published the analysis and attack chain (a malicious artifact runs code when a victim retrieves it).",
16050
+ "ai_discovered": false,
16051
+ "ai_discovery_source": "human_researcher",
16052
+ "ai_discovery_notes": "Disclosed by HiddenLayer (https://hiddenlayer.com/innovation-hub/not-so-clear-how-mlops-solutions-can-muddy-the-waters-of-your-supply-chain/). The abused surface is a widely used MLOps / experiment-tracking platform (ClearML) - the AI supply-chain layer between data scientists.",
16053
+ "ai_assisted_weaponization": false,
16054
+ "ai_assisted_notes": "No AI-assisted weaponization; the flaw is in how an MLOps platform handles uploaded experiment artifacts.",
16055
+ "active_exploitation": "none",
16056
+ "active_exploitation_notes": "Research disclosure with a documented attack chain; no confirmed in-the-wild exploitation reported as of curation. No fixed SDK version is published in the advisory, so users on the affected range remain exposed when retrieving untrusted artifacts.",
16057
+ "affected": "ClearML client SDK 0.17.0 through 1.14.2.",
16058
+ "affected_versions": [
16059
+ "ClearML (pip) >= 0.17.0, <= 1.14.2"
16060
+ ],
16061
+ "vector": "ClearML is an MLOps / experiment-tracking platform. Its client SDK stores experiment artifacts and reconstructs them on retrieval using an unsafe Python object-deserialization routine. An attacker who can upload an artifact to a project a victim will open embeds a malicious serialized object; when the victim's SDK retrieves and interacts with that artifact, the object's deserialization runs attacker code on the victim's machine (CWE-502). Disclosed by HiddenLayer.",
16062
+ "complexity": "low",
16063
+ "complexity_notes": "NVD AV:N / AC:L / PR:N / UI:R - network-delivered via an uploaded artifact, but requires the victim to retrieve/interact with it (UI:R). HiddenLayer's CNA vector marks PR:L (an account that can upload to the shared project).",
16064
+ "patch_available": false,
16065
+ "patch_required_reboot": false,
16066
+ "live_patch_available": false,
16067
+ "live_patch_tools": [],
16068
+ "live_patch_notes": "No fixed SDK version is listed in the advisory as of curation; mitigation is retrieving artifacts/datasets only from trusted projects and treating retrieved content as untrusted (see vendor_update_paths).",
16069
+ "vendor_update_paths": [
16070
+ "No fixed ClearML SDK version is listed in the GitHub advisory or NVD as of curation (HiddenLayer states the issues were resolved with the vendor within the disclosure window, but no specific fixed version is published). Only retrieve artifacts/datasets from trusted ClearML projects, run the SDK with least privilege, and treat every retrieved artifact as untrusted until the deployed SDK version is confirmed to refuse unsafe deserialization."
16071
+ ],
16072
+ "framework_control_gaps": {
16073
+ "NIST-800-53-SI-10": "Input validation is not applied to an uploaded experiment artifact/dataset before the MLOps SDK deserializes it.",
16074
+ "NIST-800-53-CM-7": "Least-functionality is not enforced: the SDK auto-deserializes artifacts through an unsafe routine on retrieval.",
16075
+ "NIST-800-53-SR-3": "Supply-chain controls do not treat MLOps experiment artifacts/datasets as untrusted third-party content delivered between collaborators.",
16076
+ "ISO-27001-2022-A.8.28": "Secure-coding expectations do not address unsafe deserialization of stored artifacts in an MLOps SDK.",
16077
+ "NIS2-Art21-supply-chain": "Supply-chain-security measures do not reach the MLOps platform as a channel that delivers executable artifacts between data scientists.",
16078
+ "DORA-Art-9": "ICT protection measures do not model MLOps-artifact retrieval as an ICT-risk event.",
16079
+ "UK-CAF-B4": "System Security objective has no objective for validating MLOps artifacts/datasets before deserialization or extraction.",
16080
+ "AU-ISM-1546": "Patch-application control does not single out MLOps client SDKs.",
16081
+ "ALL-AI-PIPELINE-INTEGRITY": "No framework treats an MLOps / experiment-tracking platform's uploaded artifacts and datasets as an untrusted code/file-delivery surface."
16082
+ },
16083
+ "atlas_refs": [
16084
+ "AML.T0010",
16085
+ "AML.T0011",
16086
+ "AML.T0011.000"
16087
+ ],
16088
+ "attack_refs": [
16089
+ "T1204",
16090
+ "T1059",
16091
+ "T1195.002"
16092
+ ],
16093
+ "rwep_score": 42,
16094
+ "rwep_factors": {
16095
+ "cisa_kev": 0,
16096
+ "poc_available": 20,
16097
+ "ai_factor": 0,
16098
+ "active_exploitation": 0,
16099
+ "blast_radius": 22,
16100
+ "patch_available": 0,
16101
+ "live_patch_available": 0,
16102
+ "reboot_required": 0
16103
+ },
16104
+ "rwep_notes": "Elevated (RWEP 42, \"patch within 7 days\" band per lib/scoring.js timeline). Not KEV, no confirmed in-the-wild exploitation, and no fixed SDK version published so no patch credit (Hard Rule #3); the UI:R requirement (victim must retrieve the malicious artifact) keeps blast moderate. poc_available=20 + blast_radius=22.",
16105
+ "epss_score": null,
16106
+ "epss_date": "2026-05-25",
16107
+ "epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
16108
+ "epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2024-24590",
16109
+ "cwe_refs": [
16110
+ "CWE-502"
16111
+ ],
16112
+ "iocs": {
16113
+ "behavioral": [
16114
+ "ClearML artifacts whose stored payload is a serialized object rather than the expected data type (a deserialization-gadget payload).",
16115
+ "The ClearML client SDK spawning shell, network, or file-system child processes immediately after an artifact is retrieved or previewed.",
16116
+ "Uploads to shared ClearML projects from accounts/users that should not be contributing artifacts.",
16117
+ "ClearML (pip) 0.17.0-1.14.2 retrieving artifacts/datasets from projects that accept untrusted uploads - the exposed precondition."
16118
+ ],
16119
+ "_ioc_source_note": "Behavioral signatures anchored to the HiddenLayer disclosure (https://hiddenlayer.com/innovation-hub/not-so-clear-how-mlops-solutions-can-muddy-the-waters-of-your-supply-chain/), the GitHub Security Advisory advisory (https://github.com/advisories/GHSA-cpcw-9h9m-wqw9), and NVD CVE-2024-24590 (CWE-502)."
16120
+ },
16121
+ "source_verified": "2026-05-25",
16122
+ "verification_sources": [
16123
+ "https://nvd.nist.gov/vuln/detail/CVE-2024-24590",
16124
+ "https://github.com/advisories/GHSA-cpcw-9h9m-wqw9",
16125
+ "https://hiddenlayer.com/innovation-hub/not-so-clear-how-mlops-solutions-can-muddy-the-waters-of-your-supply-chain/"
16126
+ ],
16127
+ "vendor_advisories": [
16128
+ {
16129
+ "vendor": "GitHub Security Advisory",
16130
+ "advisory_id": "CVE-2024-24590",
16131
+ "url": "https://github.com/advisories/GHSA-cpcw-9h9m-wqw9",
16132
+ "severity": "high",
16133
+ "published_date": "2024-06-27"
16134
+ },
16135
+ {
16136
+ "vendor": "NVD",
16137
+ "advisory_id": "CVE-2024-24590",
16138
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-24590",
16139
+ "severity": "high",
16140
+ "published_date": "2024-06-27"
16141
+ }
16142
+ ],
16143
+ "last_updated": "2026-05-25",
16144
+ "discovery_attribution_note": "Manually curated from the HiddenLayer disclosure (https://hiddenlayer.com/innovation-hub/not-so-clear-how-mlops-solutions-can-muddy-the-waters-of-your-supply-chain/) + the GitHub Security Advisory advisory (https://github.com/advisories/GHSA-cpcw-9h9m-wqw9, CWE-502) + NVD (CVSS v3.1 8.8) / HiddenLayer (CNA 8.0). MLOps / experiment-tracking platform flaw (ClearML); introduces the MLOps-artifact trust-boundary control NEW-CTRL-104.",
16145
+ "_auto_imported": false,
16146
+ "_intake_method": "manual-verified-curation",
16147
+ "_kev_short_description": "ClearML client SDK reconstructs stored artifacts through unsafe Python object-deserialization on retrieval, so a malicious artifact runs code on the retrieving user (CWE-502); no fixed SDK version is listed in the advisory - treat retrieved artifacts as untrusted."
16148
+ },
16149
+ "CVE-2024-24591": {
16150
+ "name": "ClearML Client SDK Dataset Path Traversal Arbitrary File Write",
16151
+ "type": "Arbitrary File Write",
16152
+ "cvss_score": 8.8,
16153
+ "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
16154
+ "cvss_note": "NIST (NVD) CVSS v3.1 base 8.8 (HIGH); HiddenLayer (CNA) rates it 8.0 (HIGH, PR:L). The ClearML client SDK does not constrain dataset entry paths, so a maliciously uploaded dataset writes files to an arbitrary local or remote location on the retrieving user's system (CWE-22 path traversal).",
16155
+ "cisa_kev": false,
16156
+ "poc_available": true,
16157
+ "poc_description": "HiddenLayer published the analysis and attack chain (a malicious dataset writes to arbitrary paths on retrieval).",
16158
+ "ai_discovered": false,
16159
+ "ai_discovery_source": "human_researcher",
16160
+ "ai_discovery_notes": "Disclosed by HiddenLayer (https://hiddenlayer.com/innovation-hub/not-so-clear-how-mlops-solutions-can-muddy-the-waters-of-your-supply-chain/). The abused surface is a widely used MLOps / experiment-tracking platform (ClearML) - the AI supply-chain layer between data scientists.",
16161
+ "ai_assisted_weaponization": false,
16162
+ "ai_assisted_notes": "No AI-assisted weaponization; the flaw is in how an MLOps platform handles uploaded experiment artifacts.",
16163
+ "active_exploitation": "none",
16164
+ "active_exploitation_notes": "Research disclosure with a documented attack chain; no confirmed in-the-wild exploitation reported as of curation. No fixed SDK version is published in the advisory, so users on the affected range remain exposed when retrieving untrusted artifacts.",
16165
+ "affected": "ClearML client SDK 1.4.0 through 1.14.1.",
16166
+ "affected_versions": [
16167
+ "ClearML (pip) >= 1.4.0, <= 1.14.1"
16168
+ ],
16169
+ "vector": "When the ClearML client SDK retrieves a dataset, it writes the dataset's entries to disk without constraining their paths. A maliciously uploaded dataset whose entries use absolute or ../ traversal paths therefore writes files to arbitrary locations on the retrieving user's system (CWE-22) - which, by overwriting startup or configuration files, can escalate to code execution. Disclosed by HiddenLayer.",
16170
+ "complexity": "low",
16171
+ "complexity_notes": "NVD AV:N / AC:L / PR:N / UI:R - network-delivered via an uploaded artifact, but requires the victim to retrieve/interact with it (UI:R). HiddenLayer's CNA vector marks PR:L (an account that can upload to the shared project).",
16172
+ "patch_available": false,
16173
+ "patch_required_reboot": false,
16174
+ "live_patch_available": false,
16175
+ "live_patch_tools": [],
16176
+ "live_patch_notes": "No fixed SDK version is listed in the advisory as of curation; mitigation is retrieving artifacts/datasets only from trusted projects and treating retrieved content as untrusted (see vendor_update_paths).",
16177
+ "vendor_update_paths": [
16178
+ "No fixed ClearML SDK version is listed in the GitHub advisory or NVD as of curation. Only retrieve datasets from trusted ClearML projects, run the SDK as a least-privilege user, and treat dataset extraction paths as untrusted (reject absolute / ../ traversal entries) until the deployed SDK version is confirmed to contain extraction."
16179
+ ],
16180
+ "framework_control_gaps": {
16181
+ "NIST-800-53-SI-10": "Input validation is not applied to an uploaded experiment artifact/dataset before the MLOps SDK extracts it.",
16182
+ "NIST-800-53-CM-7": "Least-functionality is not enforced: the SDK writes dataset entries without path containment on retrieval.",
16183
+ "NIST-800-53-SR-3": "Supply-chain controls do not treat MLOps experiment artifacts/datasets as untrusted third-party content delivered between collaborators.",
16184
+ "ISO-27001-2022-A.8.28": "Secure-coding expectations do not address uncontained extraction of dataset entries in an MLOps SDK.",
16185
+ "NIS2-Art21-supply-chain": "Supply-chain-security measures do not reach the MLOps platform as a channel that delivers executable artifacts between data scientists.",
16186
+ "DORA-Art-9": "ICT protection measures do not model MLOps-artifact retrieval as an ICT-risk event.",
16187
+ "UK-CAF-B4": "System Security objective has no objective for validating MLOps artifacts/datasets before deserialization or extraction.",
16188
+ "AU-ISM-1546": "Patch-application control does not single out MLOps client SDKs.",
16189
+ "ALL-AI-PIPELINE-INTEGRITY": "No framework treats an MLOps / experiment-tracking platform's uploaded artifacts and datasets as an untrusted code/file-delivery surface."
16190
+ },
16191
+ "atlas_refs": [
16192
+ "AML.T0010",
16193
+ "AML.T0049"
16194
+ ],
16195
+ "attack_refs": [
16196
+ "T1204",
16197
+ "T1083",
16198
+ "T1565.001"
16199
+ ],
16200
+ "rwep_score": 38,
16201
+ "rwep_factors": {
16202
+ "cisa_kev": 0,
16203
+ "poc_available": 20,
16204
+ "ai_factor": 0,
16205
+ "active_exploitation": 0,
16206
+ "blast_radius": 18,
16207
+ "patch_available": 0,
16208
+ "live_patch_available": 0,
16209
+ "reboot_required": 0
16210
+ },
16211
+ "rwep_notes": "Standard (RWEP 38, \"patch within 30 days\" band per lib/scoring.js timeline). Not KEV, no confirmed in-the-wild exploitation, and no fixed SDK version published so no patch credit (Hard Rule #3); the UI:R requirement (victim must retrieve the malicious artifact) keeps blast moderate. poc_available=20 + blast_radius=18.",
16212
+ "epss_score": null,
16213
+ "epss_date": "2026-05-25",
16214
+ "epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
16215
+ "epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2024-24591",
16216
+ "cwe_refs": [
16217
+ "CWE-22"
16218
+ ],
16219
+ "iocs": {
16220
+ "behavioral": [
16221
+ "ClearML datasets whose entries contain absolute paths or ../ traversal sequences.",
16222
+ "Files written by the ClearML client SDK outside the intended dataset cache/extraction directory during a dataset get.",
16223
+ "Unexpected modification of startup, configuration, or credential files following a ClearML dataset retrieval.",
16224
+ "ClearML (pip) 1.4.0-1.14.1 retrieving artifacts/datasets from projects that accept untrusted uploads - the exposed precondition."
16225
+ ],
16226
+ "_ioc_source_note": "Behavioral signatures anchored to the HiddenLayer disclosure (https://hiddenlayer.com/innovation-hub/not-so-clear-how-mlops-solutions-can-muddy-the-waters-of-your-supply-chain/), the GitHub Security Advisory advisory (https://github.com/advisories/GHSA-m95h-p4gg-wfw3), and NVD CVE-2024-24591 (CWE-22)."
16227
+ },
16228
+ "source_verified": "2026-05-25",
16229
+ "verification_sources": [
16230
+ "https://nvd.nist.gov/vuln/detail/CVE-2024-24591",
16231
+ "https://github.com/advisories/GHSA-m95h-p4gg-wfw3",
16232
+ "https://hiddenlayer.com/innovation-hub/not-so-clear-how-mlops-solutions-can-muddy-the-waters-of-your-supply-chain/"
16233
+ ],
16234
+ "vendor_advisories": [
16235
+ {
16236
+ "vendor": "GitHub Security Advisory",
16237
+ "advisory_id": "CVE-2024-24591",
16238
+ "url": "https://github.com/advisories/GHSA-m95h-p4gg-wfw3",
16239
+ "severity": "high",
16240
+ "published_date": "2024-06-27"
16241
+ },
16242
+ {
16243
+ "vendor": "NVD",
16244
+ "advisory_id": "CVE-2024-24591",
16245
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-24591",
16246
+ "severity": "high",
16247
+ "published_date": "2024-06-27"
16248
+ }
16249
+ ],
16250
+ "last_updated": "2026-05-25",
16251
+ "discovery_attribution_note": "Manually curated from the HiddenLayer disclosure (https://hiddenlayer.com/innovation-hub/not-so-clear-how-mlops-solutions-can-muddy-the-waters-of-your-supply-chain/) + the GitHub Security Advisory advisory (https://github.com/advisories/GHSA-m95h-p4gg-wfw3, CWE-22) + NVD (CVSS v3.1 8.8) / HiddenLayer (CNA 8.0). MLOps / experiment-tracking platform flaw (ClearML); introduces the MLOps-artifact trust-boundary control NEW-CTRL-104.",
16252
+ "_auto_imported": false,
16253
+ "_intake_method": "manual-verified-curation",
16254
+ "_kev_short_description": "ClearML client SDK writes dataset entries without path containment, so a malicious dataset writes files to arbitrary paths on the retrieving user (CWE-22 path traversal); no fixed SDK version is listed in the advisory - retrieve datasets only from trusted projects."
16255
+ },
15916
16256
  "CVE-2026-41091": {
15917
16257
  "name": "Microsoft Defender (Malware Protection Engine) Link-Following LPE to SYSTEM",
15918
16258
  "type": "LPE",
@@ -101,6 +101,7 @@
101
101
  "CVE-2024-13059",
102
102
  "CVE-2024-1561",
103
103
  "CVE-2024-1708",
104
+ "CVE-2024-24591",
104
105
  "CVE-2024-37032",
105
106
  "CVE-2024-39722",
106
107
  "CVE-2024-57728",
@@ -391,6 +392,7 @@
391
392
  "CVE-2025-11837",
392
393
  "CVE-2025-1550",
393
394
  "CVE-2025-32432",
395
+ "CVE-2025-3248",
394
396
  "CVE-2025-33236",
395
397
  "CVE-2025-37164",
396
398
  "CVE-2025-43200",
@@ -750,6 +752,7 @@
750
752
  "evidence_cves": [
751
753
  "CVE-2020-24363",
752
754
  "CVE-2025-32433",
755
+ "CVE-2025-3248",
753
756
  "CVE-2025-4008",
754
757
  "CVE-2025-49596",
755
758
  "CVE-2025-61757",
@@ -1333,6 +1336,7 @@
1333
1336
  "CVE-2024-11392",
1334
1337
  "CVE-2024-11393",
1335
1338
  "CVE-2024-11394",
1339
+ "CVE-2024-24590",
1336
1340
  "CVE-2024-50050",
1337
1341
  "CVE-2024-8069",
1338
1342
  "CVE-2025-10035",