@blamejs/exceptd-skills 0.13.83 → 0.13.84
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.
- package/CHANGELOG.md +4 -0
- package/data/_indexes/_meta.json +9 -9
- package/data/_indexes/activity-feed.json +2 -2
- package/data/_indexes/catalog-summaries.json +2 -2
- package/data/_indexes/chains.json +1368 -0
- package/data/atlas-ttps.json +4 -1
- package/data/attack-techniques.json +5 -0
- package/data/cve-catalog.json +313 -1
- package/data/cwe-catalog.json +4 -0
- package/data/framework-control-gaps.json +24 -0
- package/data/zeroday-lessons.json +150 -0
- package/manifest.json +44 -44
- package/package.json +2 -2
- package/sbom.cdx.json +25 -25
package/data/atlas-ttps.json
CHANGED
|
@@ -1702,8 +1702,11 @@
|
|
|
1702
1702
|
"is_subtechnique": false,
|
|
1703
1703
|
"cve_refs": [
|
|
1704
1704
|
"CVE-2023-48022",
|
|
1705
|
+
"CVE-2024-42478",
|
|
1706
|
+
"CVE-2024-42479",
|
|
1705
1707
|
"CVE-2025-64496",
|
|
1706
|
-
"CVE-2026-0766"
|
|
1708
|
+
"CVE-2026-0766",
|
|
1709
|
+
"CVE-2026-34159"
|
|
1707
1710
|
]
|
|
1708
1711
|
},
|
|
1709
1712
|
"AML.T0050": {
|
|
@@ -270,6 +270,7 @@
|
|
|
270
270
|
],
|
|
271
271
|
"cve_refs": [
|
|
272
272
|
"CVE-2023-48022",
|
|
273
|
+
"CVE-2024-42479",
|
|
273
274
|
"CVE-2024-50050",
|
|
274
275
|
"CVE-2025-1094",
|
|
275
276
|
"CVE-2025-11837",
|
|
@@ -298,6 +299,7 @@
|
|
|
298
299
|
"CVE-2026-30624",
|
|
299
300
|
"CVE-2026-30625",
|
|
300
301
|
"CVE-2026-32202",
|
|
302
|
+
"CVE-2026-34159",
|
|
301
303
|
"CVE-2026-39884",
|
|
302
304
|
"CVE-2026-39987",
|
|
303
305
|
"CVE-2026-40933",
|
|
@@ -836,6 +838,8 @@
|
|
|
836
838
|
"CVE-2024-1709",
|
|
837
839
|
"CVE-2024-21762",
|
|
838
840
|
"CVE-2024-37079",
|
|
841
|
+
"CVE-2024-42478",
|
|
842
|
+
"CVE-2024-42479",
|
|
839
843
|
"CVE-2024-43468",
|
|
840
844
|
"CVE-2024-50050",
|
|
841
845
|
"CVE-2024-56145",
|
|
@@ -985,6 +989,7 @@
|
|
|
985
989
|
"CVE-2026-32202",
|
|
986
990
|
"CVE-2026-33017",
|
|
987
991
|
"CVE-2026-33634",
|
|
992
|
+
"CVE-2026-34159",
|
|
988
993
|
"CVE-2026-34197",
|
|
989
994
|
"CVE-2026-34621",
|
|
990
995
|
"CVE-2026-3502",
|
package/data/cve-catalog.json
CHANGED
|
@@ -55,7 +55,7 @@
|
|
|
55
55
|
"ai_discovery_methodology": {
|
|
56
56
|
"field_added": "2026-05-15",
|
|
57
57
|
"agents_md_target": "Hard Rule #7 — '41% of 2025 zero-days were AI-discovered'. Catalog target rate floor: 0.40.",
|
|
58
|
-
"current_rate": 0.
|
|
58
|
+
"current_rate": 0.034,
|
|
59
59
|
"current_floor_enforced_by_test": 0.03,
|
|
60
60
|
"ladder_to_target": [
|
|
61
61
|
0.03,
|
|
@@ -12035,6 +12035,318 @@
|
|
|
12035
12035
|
"_intake_method": "manual-verified-curation",
|
|
12036
12036
|
"_kev_short_description": "Keras safe_mode (added for CVE-2025-1550) is bypassable through 3.10.0: a crafted .keras archive executes code via built-in module arguments even with safe_mode on (CWE-502). The first fix was incomplete."
|
|
12037
12037
|
},
|
|
12038
|
+
"CVE-2024-42479": {
|
|
12039
|
+
"name": "llama.cpp RPC Backend SET_TENSOR Out-of-Bounds Write RCE",
|
|
12040
|
+
"type": "RCE",
|
|
12041
|
+
"cvss_score": 9.8,
|
|
12042
|
+
"cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
|
|
12043
|
+
"cvss_note": "NIST CVSS v3.1 base 9.8 (CRITICAL); GitHub scored it 10.0 (Scope:Changed). An unsafe data pointer in the rpc_tensor struct enables a write-what-where primitive (CWE-787/CWE-123).",
|
|
12044
|
+
"cisa_kev": false,
|
|
12045
|
+
"poc_available": true,
|
|
12046
|
+
"poc_description": "Public exploitation research exists (pwner.gg and retr0.blog walkthroughs of llama.cpp RPC RCE): an unauthenticated TCP client to the RPC server sends crafted rpc_tensor messages to read/write arbitrary memory and, chaining the primitives, execute code.",
|
|
12047
|
+
"ai_discovered": false,
|
|
12048
|
+
"ai_discovery_source": "human_researcher",
|
|
12049
|
+
"ai_discovery_notes": "Disclosed via llama.cpp (ggml) GitHub security advisories and independent exploitation research. The abused surface is the distributed-inference RPC backend of the most widely used local LLM runtime.",
|
|
12050
|
+
"ai_assisted_weaponization": false,
|
|
12051
|
+
"ai_assisted_notes": "No AI-assisted weaponization; classic memory-safety in the inference RPC backend, notable for the incomplete first fix.",
|
|
12052
|
+
"active_exploitation": "none",
|
|
12053
|
+
"active_exploitation_notes": "Advisory / research disclosure with a coordinated fix; no confirmed in-the-wild exploitation reported as of curation.",
|
|
12054
|
+
"affected": "llama.cpp prior to build b3561.",
|
|
12055
|
+
"affected_versions": [
|
|
12056
|
+
"llama.cpp < b3561"
|
|
12057
|
+
],
|
|
12058
|
+
"vector": "llama.cpp's RPC backend deserializes a rpc_tensor whose data pointer is attacker-controlled and unvalidated, so a SET_TENSOR message yields an arbitrary-address write (write-what-where, CWE-123). An unauthenticated attacker with TCP access to the RPC server (default port 50052) achieves remote code execution.",
|
|
12059
|
+
"complexity": "low",
|
|
12060
|
+
"complexity_notes": "NVD AV:N / AC:L / PR:N — unauthenticated TCP access to the RPC server (default port 50052).",
|
|
12061
|
+
"patch_available": true,
|
|
12062
|
+
"patch_required_reboot": false,
|
|
12063
|
+
"live_patch_available": false,
|
|
12064
|
+
"live_patch_tools": [],
|
|
12065
|
+
"live_patch_notes": "Remediation is upgrading llama.cpp to build b3561 or later; rebuild/redeploy, no host reboot.",
|
|
12066
|
+
"vendor_update_paths": [
|
|
12067
|
+
"Upgrade llama.cpp to build b3561 or later. Never expose the RPC server (default port 50052) to untrusted networks; it has no authentication. Bind it to localhost or a trusted segment and run least-privilege."
|
|
12068
|
+
],
|
|
12069
|
+
"framework_control_gaps": {
|
|
12070
|
+
"NIST-800-53-SI-2": "Flaw-remediation cadence does not track the local-LLM runtime's RPC backend as managed, RCE-bearing software, nor that the first fix left the GRAPH_COMPUTE path unpatched.",
|
|
12071
|
+
"NIST-800-53-SC-7": "Boundary-protection control does not flag the unauthenticated RPC server (port 50052) as a network-exposed execution surface.",
|
|
12072
|
+
"ISO-27001-2022-A.8.8": "Vulnerability management rarely enumerates the inference RPC backend's tensor deserialization as a memory-safety surface.",
|
|
12073
|
+
"NIS2-Art21-patch-management": "Article 21 measures do not reach the inference RPC backend as a privileged, unauthenticated control plane.",
|
|
12074
|
+
"DORA-Art-9": "ICT protection measures do not model an unauthenticated inference-RPC memory-corruption RCE as an ICT-risk event.",
|
|
12075
|
+
"UK-CAF-B4": "System Security objective has no objective for validating deserialized tensor bounds in the inference RPC backend.",
|
|
12076
|
+
"AU-ISM-1546": "Patch-application control does not single out the local-LLM runtime's RPC backend.",
|
|
12077
|
+
"ALL-AI-PIPELINE-INTEGRITY": "No framework treats the inference RPC backend's deserialized tensors as untrusted input requiring bounds validation on every command path; per-command patching left GRAPH_COMPUTE exploitable."
|
|
12078
|
+
},
|
|
12079
|
+
"atlas_refs": [
|
|
12080
|
+
"AML.T0049"
|
|
12081
|
+
],
|
|
12082
|
+
"attack_refs": [
|
|
12083
|
+
"T1190",
|
|
12084
|
+
"T1059"
|
|
12085
|
+
],
|
|
12086
|
+
"rwep_score": 29,
|
|
12087
|
+
"rwep_factors": {
|
|
12088
|
+
"cisa_kev": 0,
|
|
12089
|
+
"poc_available": 20,
|
|
12090
|
+
"ai_factor": 0,
|
|
12091
|
+
"active_exploitation": 0,
|
|
12092
|
+
"blast_radius": 24,
|
|
12093
|
+
"patch_available": -15,
|
|
12094
|
+
"live_patch_available": 0,
|
|
12095
|
+
"reboot_required": 0
|
|
12096
|
+
},
|
|
12097
|
+
"rwep_notes": "Standard (RWEP 29, \"patch within 30 days\" band per lib/scoring.js timeline). Not KEV, no confirmed in-the-wild exploitation, patched at/after disclosure (Hard Rule #3). poc_available=20 + blast_radius=24 (llama.cpp is the most widely used local LLM runtime) minus patch 15. Note: unauthenticated network reachability of the RPC server raises operational urgency beyond the RWEP number.",
|
|
12098
|
+
"epss_score": null,
|
|
12099
|
+
"epss_date": "2026-05-25",
|
|
12100
|
+
"epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
|
|
12101
|
+
"epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2024-42479",
|
|
12102
|
+
"cwe_refs": [
|
|
12103
|
+
"CWE-787",
|
|
12104
|
+
"CWE-123"
|
|
12105
|
+
],
|
|
12106
|
+
"iocs": {
|
|
12107
|
+
"behavioral": [
|
|
12108
|
+
"Inbound TCP connections to the llama.cpp RPC server (default port 50052) from untrusted hosts.",
|
|
12109
|
+
"RPC messages carrying rpc_tensor structures with a data pointer or buffer field that does not reference a server-allocated buffer (buffer=0 / out-of-range).",
|
|
12110
|
+
"llama.cpp RPC worker crashes, anomalous memory access, or process spawning following GRAPH_COMPUTE / SET_TENSOR / GET_TENSOR traffic.",
|
|
12111
|
+
"llama.cpp at an affected build (llama.cpp < b3561) with the RPC server reachable from untrusted networks — the exposed precondition."
|
|
12112
|
+
],
|
|
12113
|
+
"_ioc_source_note": "Behavioral signatures derived from the ggml/llama.cpp GitHub security advisory (https://github.com/ggerganov/llama.cpp/security/advisories/GHSA-wcr5-566p-9cwj) and the public exploitation research (https://pwner.gg/blog/2024-10-03-llama-cpp-cves ; https://retr0.blog/blog/llama-rpc-rce), plus NVD CVE-2024-42479 (CWE-787/CWE-123). The unvalidated rpc_tensor data pointer / buffer=0 deserialization is the indicator anchor."
|
|
12114
|
+
},
|
|
12115
|
+
"source_verified": "2026-05-25",
|
|
12116
|
+
"verification_sources": [
|
|
12117
|
+
"https://nvd.nist.gov/vuln/detail/CVE-2024-42479",
|
|
12118
|
+
"https://github.com/ggerganov/llama.cpp/security/advisories/GHSA-wcr5-566p-9cwj",
|
|
12119
|
+
"https://pwner.gg/blog/2024-10-03-llama-cpp-cves"
|
|
12120
|
+
],
|
|
12121
|
+
"vendor_advisories": [
|
|
12122
|
+
{
|
|
12123
|
+
"vendor": "GitHub Security Advisory",
|
|
12124
|
+
"advisory_id": "CVE-2024-42479",
|
|
12125
|
+
"url": "https://github.com/ggerganov/llama.cpp/security/advisories/GHSA-wcr5-566p-9cwj",
|
|
12126
|
+
"severity": "critical",
|
|
12127
|
+
"published_date": "2024-08-12"
|
|
12128
|
+
},
|
|
12129
|
+
{
|
|
12130
|
+
"vendor": "NVD",
|
|
12131
|
+
"advisory_id": "CVE-2024-42479",
|
|
12132
|
+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42479",
|
|
12133
|
+
"severity": "critical",
|
|
12134
|
+
"published_date": "2024-08-12"
|
|
12135
|
+
}
|
|
12136
|
+
],
|
|
12137
|
+
"last_updated": "2026-05-25",
|
|
12138
|
+
"discovery_attribution_note": "Manually curated from NVD (CWE-787/CWE-123; NIST CVSS 9.8) + the ggml/llama.cpp GitHub security advisory + public exploitation research. Member of the llama.cpp RPC-backend memory-safety family; CVE-2026-34159 is the GRAPH_COMPUTE path the b3561 fix for CVE-2024-42478/42479 left unpatched.",
|
|
12139
|
+
"_auto_imported": false,
|
|
12140
|
+
"_intake_method": "manual-verified-curation",
|
|
12141
|
+
"_kev_short_description": "llama.cpp's RPC backend SET_TENSOR uses an unvalidated rpc_tensor data pointer, giving an unauthenticated attacker a write-what-where primitive and RCE; fixed in b3561."
|
|
12142
|
+
},
|
|
12143
|
+
"CVE-2024-42478": {
|
|
12144
|
+
"name": "llama.cpp RPC Backend GET_TENSOR Out-of-Bounds Read",
|
|
12145
|
+
"type": "INFO-DISCLOSURE",
|
|
12146
|
+
"cvss_score": 9.8,
|
|
12147
|
+
"cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
|
|
12148
|
+
"cvss_note": "NIST CVSS v3.1 base 9.8 (CRITICAL). An unsafe data pointer in the rpc_tensor struct enables arbitrary-address reads (CWE-125), a primitive for pointer leaks / ASLR bypass that chains into the write-what-where RCE.",
|
|
12149
|
+
"cisa_kev": false,
|
|
12150
|
+
"poc_available": true,
|
|
12151
|
+
"poc_description": "Public exploitation research exists (pwner.gg and retr0.blog walkthroughs of llama.cpp RPC RCE): an unauthenticated TCP client to the RPC server sends crafted rpc_tensor messages to read/write arbitrary memory and, chaining the primitives, execute code.",
|
|
12152
|
+
"ai_discovered": false,
|
|
12153
|
+
"ai_discovery_source": "human_researcher",
|
|
12154
|
+
"ai_discovery_notes": "Disclosed via llama.cpp (ggml) GitHub security advisories and independent exploitation research. The abused surface is the distributed-inference RPC backend of the most widely used local LLM runtime.",
|
|
12155
|
+
"ai_assisted_weaponization": false,
|
|
12156
|
+
"ai_assisted_notes": "No AI-assisted weaponization; classic memory-safety in the inference RPC backend, notable for the incomplete first fix.",
|
|
12157
|
+
"active_exploitation": "none",
|
|
12158
|
+
"active_exploitation_notes": "Advisory / research disclosure with a coordinated fix; no confirmed in-the-wild exploitation reported as of curation.",
|
|
12159
|
+
"affected": "llama.cpp prior to build b3561.",
|
|
12160
|
+
"affected_versions": [
|
|
12161
|
+
"llama.cpp < b3561"
|
|
12162
|
+
],
|
|
12163
|
+
"vector": "llama.cpp's RPC backend deserializes a rpc_tensor whose data pointer is attacker-controlled and unvalidated, so a GET_TENSOR message yields an arbitrary-address read (CWE-125). An unauthenticated attacker with TCP access to the RPC server leaks memory (pointers, ASLR bypass), enabling reliable exploitation of the companion write primitive.",
|
|
12164
|
+
"complexity": "low",
|
|
12165
|
+
"complexity_notes": "NVD AV:N / AC:L / PR:N — unauthenticated TCP access to the RPC server (default port 50052).",
|
|
12166
|
+
"patch_available": true,
|
|
12167
|
+
"patch_required_reboot": false,
|
|
12168
|
+
"live_patch_available": false,
|
|
12169
|
+
"live_patch_tools": [],
|
|
12170
|
+
"live_patch_notes": "Remediation is upgrading llama.cpp to build b3561 or later; rebuild/redeploy, no host reboot.",
|
|
12171
|
+
"vendor_update_paths": [
|
|
12172
|
+
"Upgrade llama.cpp to build b3561 or later. Never expose the RPC server (default port 50052) to untrusted networks; it has no authentication. Bind it to localhost or a trusted segment and run least-privilege."
|
|
12173
|
+
],
|
|
12174
|
+
"framework_control_gaps": {
|
|
12175
|
+
"NIST-800-53-SI-2": "Flaw-remediation cadence does not track the local-LLM runtime's RPC backend as managed, RCE-bearing software, nor that the first fix left the GRAPH_COMPUTE path unpatched.",
|
|
12176
|
+
"NIST-800-53-SC-7": "Boundary-protection control does not flag the unauthenticated RPC server (port 50052) as a network-exposed execution surface.",
|
|
12177
|
+
"ISO-27001-2022-A.8.8": "Vulnerability management rarely enumerates the inference RPC backend's tensor deserialization as a memory-safety surface.",
|
|
12178
|
+
"NIS2-Art21-patch-management": "Article 21 measures do not reach the inference RPC backend as a privileged, unauthenticated control plane.",
|
|
12179
|
+
"DORA-Art-9": "ICT protection measures do not model an unauthenticated inference-RPC memory-corruption RCE as an ICT-risk event.",
|
|
12180
|
+
"UK-CAF-B4": "System Security objective has no objective for validating deserialized tensor bounds in the inference RPC backend.",
|
|
12181
|
+
"AU-ISM-1546": "Patch-application control does not single out the local-LLM runtime's RPC backend.",
|
|
12182
|
+
"ALL-AI-PIPELINE-INTEGRITY": "No framework treats the inference RPC backend's deserialized tensors as untrusted input requiring bounds validation on every command path; per-command patching left GRAPH_COMPUTE exploitable."
|
|
12183
|
+
},
|
|
12184
|
+
"atlas_refs": [
|
|
12185
|
+
"AML.T0049"
|
|
12186
|
+
],
|
|
12187
|
+
"attack_refs": [
|
|
12188
|
+
"T1190"
|
|
12189
|
+
],
|
|
12190
|
+
"rwep_score": 29,
|
|
12191
|
+
"rwep_factors": {
|
|
12192
|
+
"cisa_kev": 0,
|
|
12193
|
+
"poc_available": 20,
|
|
12194
|
+
"ai_factor": 0,
|
|
12195
|
+
"active_exploitation": 0,
|
|
12196
|
+
"blast_radius": 24,
|
|
12197
|
+
"patch_available": -15,
|
|
12198
|
+
"live_patch_available": 0,
|
|
12199
|
+
"reboot_required": 0
|
|
12200
|
+
},
|
|
12201
|
+
"rwep_notes": "Standard (RWEP 29, \"patch within 30 days\" band per lib/scoring.js timeline). Not KEV, no confirmed in-the-wild exploitation, patched at/after disclosure (Hard Rule #3). poc_available=20 + blast_radius=24 (llama.cpp is the most widely used local LLM runtime) minus patch 15. Note: unauthenticated network reachability of the RPC server raises operational urgency beyond the RWEP number.",
|
|
12202
|
+
"epss_score": null,
|
|
12203
|
+
"epss_date": "2026-05-25",
|
|
12204
|
+
"epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
|
|
12205
|
+
"epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2024-42478",
|
|
12206
|
+
"cwe_refs": [
|
|
12207
|
+
"CWE-125"
|
|
12208
|
+
],
|
|
12209
|
+
"iocs": {
|
|
12210
|
+
"behavioral": [
|
|
12211
|
+
"Inbound TCP connections to the llama.cpp RPC server (default port 50052) from untrusted hosts.",
|
|
12212
|
+
"RPC messages carrying rpc_tensor structures with a data pointer or buffer field that does not reference a server-allocated buffer (buffer=0 / out-of-range).",
|
|
12213
|
+
"llama.cpp RPC worker crashes, anomalous memory access, or process spawning following GRAPH_COMPUTE / SET_TENSOR / GET_TENSOR traffic.",
|
|
12214
|
+
"llama.cpp at an affected build (llama.cpp < b3561) with the RPC server reachable from untrusted networks — the exposed precondition."
|
|
12215
|
+
],
|
|
12216
|
+
"_ioc_source_note": "Behavioral signatures derived from the ggml/llama.cpp GitHub security advisory (https://github.com/ggerganov/llama.cpp/security/advisories/GHSA-5vm9-p64x-gqw9) and the public exploitation research (https://pwner.gg/blog/2024-10-03-llama-cpp-cves ; https://retr0.blog/blog/llama-rpc-rce), plus NVD CVE-2024-42478 (CWE-125). The unvalidated rpc_tensor data pointer / buffer=0 deserialization is the indicator anchor."
|
|
12217
|
+
},
|
|
12218
|
+
"source_verified": "2026-05-25",
|
|
12219
|
+
"verification_sources": [
|
|
12220
|
+
"https://nvd.nist.gov/vuln/detail/CVE-2024-42478",
|
|
12221
|
+
"https://github.com/ggerganov/llama.cpp/security/advisories/GHSA-5vm9-p64x-gqw9",
|
|
12222
|
+
"https://pwner.gg/blog/2024-10-03-llama-cpp-cves"
|
|
12223
|
+
],
|
|
12224
|
+
"vendor_advisories": [
|
|
12225
|
+
{
|
|
12226
|
+
"vendor": "GitHub Security Advisory",
|
|
12227
|
+
"advisory_id": "CVE-2024-42478",
|
|
12228
|
+
"url": "https://github.com/ggerganov/llama.cpp/security/advisories/GHSA-5vm9-p64x-gqw9",
|
|
12229
|
+
"severity": "critical",
|
|
12230
|
+
"published_date": "2024-08-12"
|
|
12231
|
+
},
|
|
12232
|
+
{
|
|
12233
|
+
"vendor": "NVD",
|
|
12234
|
+
"advisory_id": "CVE-2024-42478",
|
|
12235
|
+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42478",
|
|
12236
|
+
"severity": "critical",
|
|
12237
|
+
"published_date": "2024-08-12"
|
|
12238
|
+
}
|
|
12239
|
+
],
|
|
12240
|
+
"last_updated": "2026-05-25",
|
|
12241
|
+
"discovery_attribution_note": "Manually curated from NVD (CWE-125; NIST CVSS 9.8) + the ggml/llama.cpp GitHub security advisory + public exploitation research. Member of the llama.cpp RPC-backend memory-safety family; CVE-2026-34159 is the GRAPH_COMPUTE path the b3561 fix for CVE-2024-42478/42479 left unpatched.",
|
|
12242
|
+
"_auto_imported": false,
|
|
12243
|
+
"_intake_method": "manual-verified-curation",
|
|
12244
|
+
"_kev_short_description": "llama.cpp's RPC backend GET_TENSOR uses an unvalidated rpc_tensor data pointer, giving an unauthenticated attacker an arbitrary-address read (pointer leak / ASLR bypass); fixed in b3561."
|
|
12245
|
+
},
|
|
12246
|
+
"CVE-2026-34159": {
|
|
12247
|
+
"name": "llama.cpp RPC Backend GRAPH_COMPUTE deserialize_tensor Bounds Bypass RCE",
|
|
12248
|
+
"type": "RCE",
|
|
12249
|
+
"cvss_score": 9.8,
|
|
12250
|
+
"cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
|
|
12251
|
+
"cvss_note": "NVD CVSS v3.1 base 9.8 (CRITICAL). deserialize_tensor() skips all bounds validation when a tensor's buffer field is 0 (CWE-119); the 2024 GET/SET_TENSOR fix (b3561) never covered the GRAPH_COMPUTE command path.",
|
|
12252
|
+
"cisa_kev": false,
|
|
12253
|
+
"poc_available": true,
|
|
12254
|
+
"poc_description": "Public exploitation research exists (pwner.gg and retr0.blog walkthroughs of llama.cpp RPC RCE): an unauthenticated TCP client to the RPC server sends crafted rpc_tensor messages to read/write arbitrary memory and, chaining the primitives, execute code.",
|
|
12255
|
+
"ai_discovered": false,
|
|
12256
|
+
"ai_discovery_source": "human_researcher",
|
|
12257
|
+
"ai_discovery_notes": "Disclosed via llama.cpp (ggml) GitHub security advisories and independent exploitation research. The abused surface is the distributed-inference RPC backend of the most widely used local LLM runtime.",
|
|
12258
|
+
"ai_assisted_weaponization": false,
|
|
12259
|
+
"ai_assisted_notes": "No AI-assisted weaponization; classic memory-safety in the inference RPC backend, notable for the incomplete first fix.",
|
|
12260
|
+
"active_exploitation": "none",
|
|
12261
|
+
"active_exploitation_notes": "Advisory / research disclosure with a coordinated fix; no confirmed in-the-wild exploitation reported as of curation.",
|
|
12262
|
+
"affected": "llama.cpp prior to build b8492 (the GRAPH_COMPUTE path was not covered by the b3561 fix for CVE-2024-42478 / CVE-2024-42479).",
|
|
12263
|
+
"affected_versions": [
|
|
12264
|
+
"llama.cpp < b8492"
|
|
12265
|
+
],
|
|
12266
|
+
"vector": "llama.cpp's RPC backend deserialize_tensor() skips bounds validation when a tensor's buffer field is 0 (CWE-119). Because the b3561 fix only hardened the GET_TENSOR / SET_TENSOR handlers, a malicious GRAPH_COMPUTE message still reaches the unvalidated path, giving an unauthenticated attacker arbitrary memory read/write, ASLR bypass, and remote code execution.",
|
|
12267
|
+
"complexity": "low",
|
|
12268
|
+
"complexity_notes": "NVD AV:N / AC:L / PR:N — unauthenticated TCP access to the RPC server (default port 50052).",
|
|
12269
|
+
"patch_available": true,
|
|
12270
|
+
"patch_required_reboot": false,
|
|
12271
|
+
"live_patch_available": false,
|
|
12272
|
+
"live_patch_tools": [],
|
|
12273
|
+
"live_patch_notes": "Remediation is upgrading llama.cpp to build b8492 or later; rebuild/redeploy, no host reboot.",
|
|
12274
|
+
"vendor_update_paths": [
|
|
12275
|
+
"Upgrade llama.cpp to build b8492 or later. Never expose the RPC server (default port 50052) to untrusted networks; it has no authentication. Bind it to localhost or a trusted segment and run least-privilege."
|
|
12276
|
+
],
|
|
12277
|
+
"framework_control_gaps": {
|
|
12278
|
+
"NIST-800-53-SI-2": "Flaw-remediation cadence does not track the local-LLM runtime's RPC backend as managed, RCE-bearing software, nor that the first fix left the GRAPH_COMPUTE path unpatched.",
|
|
12279
|
+
"NIST-800-53-SC-7": "Boundary-protection control does not flag the unauthenticated RPC server (port 50052) as a network-exposed execution surface.",
|
|
12280
|
+
"ISO-27001-2022-A.8.8": "Vulnerability management rarely enumerates the inference RPC backend's tensor deserialization as a memory-safety surface.",
|
|
12281
|
+
"NIS2-Art21-patch-management": "Article 21 measures do not reach the inference RPC backend as a privileged, unauthenticated control plane.",
|
|
12282
|
+
"DORA-Art-9": "ICT protection measures do not model an unauthenticated inference-RPC memory-corruption RCE as an ICT-risk event.",
|
|
12283
|
+
"UK-CAF-B4": "System Security objective has no objective for validating deserialized tensor bounds in the inference RPC backend.",
|
|
12284
|
+
"AU-ISM-1546": "Patch-application control does not single out the local-LLM runtime's RPC backend.",
|
|
12285
|
+
"ALL-AI-PIPELINE-INTEGRITY": "No framework treats the inference RPC backend's deserialized tensors as untrusted input requiring bounds validation on every command path; per-command patching left GRAPH_COMPUTE exploitable."
|
|
12286
|
+
},
|
|
12287
|
+
"atlas_refs": [
|
|
12288
|
+
"AML.T0049"
|
|
12289
|
+
],
|
|
12290
|
+
"attack_refs": [
|
|
12291
|
+
"T1190",
|
|
12292
|
+
"T1059"
|
|
12293
|
+
],
|
|
12294
|
+
"rwep_score": 29,
|
|
12295
|
+
"rwep_factors": {
|
|
12296
|
+
"cisa_kev": 0,
|
|
12297
|
+
"poc_available": 20,
|
|
12298
|
+
"ai_factor": 0,
|
|
12299
|
+
"active_exploitation": 0,
|
|
12300
|
+
"blast_radius": 24,
|
|
12301
|
+
"patch_available": -15,
|
|
12302
|
+
"live_patch_available": 0,
|
|
12303
|
+
"reboot_required": 0
|
|
12304
|
+
},
|
|
12305
|
+
"rwep_notes": "Standard (RWEP 29, \"patch within 30 days\" band per lib/scoring.js timeline). Not KEV, no confirmed in-the-wild exploitation, patched at/after disclosure (Hard Rule #3). poc_available=20 + blast_radius=24 (llama.cpp is the most widely used local LLM runtime) minus patch 15. Note: unauthenticated network reachability of the RPC server raises operational urgency beyond the RWEP number.",
|
|
12306
|
+
"epss_score": null,
|
|
12307
|
+
"epss_date": "2026-05-25",
|
|
12308
|
+
"epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
|
|
12309
|
+
"epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2026-34159",
|
|
12310
|
+
"cwe_refs": [
|
|
12311
|
+
"CWE-119"
|
|
12312
|
+
],
|
|
12313
|
+
"iocs": {
|
|
12314
|
+
"behavioral": [
|
|
12315
|
+
"Inbound TCP connections to the llama.cpp RPC server (default port 50052) from untrusted hosts.",
|
|
12316
|
+
"RPC messages carrying rpc_tensor structures with a data pointer or buffer field that does not reference a server-allocated buffer (buffer=0 / out-of-range).",
|
|
12317
|
+
"llama.cpp RPC worker crashes, anomalous memory access, or process spawning following GRAPH_COMPUTE / SET_TENSOR / GET_TENSOR traffic.",
|
|
12318
|
+
"llama.cpp at an affected build (llama.cpp < b8492) with the RPC server reachable from untrusted networks — the exposed precondition."
|
|
12319
|
+
],
|
|
12320
|
+
"_ioc_source_note": "Behavioral signatures derived from the ggml/llama.cpp GitHub security advisory (https://github.com/ggml-org/llama.cpp/security/advisories/GHSA-j8rj-fmpv-wcxw) and the public exploitation research (https://pwner.gg/blog/2024-10-03-llama-cpp-cves ; https://retr0.blog/blog/llama-rpc-rce), plus NVD CVE-2026-34159 (CWE-119). The unvalidated rpc_tensor data pointer / buffer=0 deserialization is the indicator anchor."
|
|
12321
|
+
},
|
|
12322
|
+
"source_verified": "2026-05-25",
|
|
12323
|
+
"verification_sources": [
|
|
12324
|
+
"https://nvd.nist.gov/vuln/detail/CVE-2026-34159",
|
|
12325
|
+
"https://github.com/ggml-org/llama.cpp/security/advisories/GHSA-j8rj-fmpv-wcxw",
|
|
12326
|
+
"https://pwner.gg/blog/2024-10-03-llama-cpp-cves"
|
|
12327
|
+
],
|
|
12328
|
+
"vendor_advisories": [
|
|
12329
|
+
{
|
|
12330
|
+
"vendor": "GitHub Security Advisory",
|
|
12331
|
+
"advisory_id": "CVE-2026-34159",
|
|
12332
|
+
"url": "https://github.com/ggml-org/llama.cpp/security/advisories/GHSA-j8rj-fmpv-wcxw",
|
|
12333
|
+
"severity": "critical",
|
|
12334
|
+
"published_date": "2026-04-01"
|
|
12335
|
+
},
|
|
12336
|
+
{
|
|
12337
|
+
"vendor": "NVD",
|
|
12338
|
+
"advisory_id": "CVE-2026-34159",
|
|
12339
|
+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34159",
|
|
12340
|
+
"severity": "critical",
|
|
12341
|
+
"published_date": "2026-04-01"
|
|
12342
|
+
}
|
|
12343
|
+
],
|
|
12344
|
+
"last_updated": "2026-05-25",
|
|
12345
|
+
"discovery_attribution_note": "Manually curated from NVD (CWE-119; NIST CVSS 9.8) + the ggml/llama.cpp GitHub security advisory + public exploitation research. Member of the llama.cpp RPC-backend memory-safety family; CVE-2026-34159 is the GRAPH_COMPUTE path the b3561 fix for CVE-2024-42478/42479 left unpatched.",
|
|
12346
|
+
"_auto_imported": false,
|
|
12347
|
+
"_intake_method": "manual-verified-curation",
|
|
12348
|
+
"_kev_short_description": "llama.cpp's RPC backend deserialize_tensor() still skips bounds checks via GRAPH_COMPUTE (buffer=0) — the GRAPH_COMPUTE path the b3561 fix missed — giving unauthenticated RCE; fixed in b8492."
|
|
12349
|
+
},
|
|
12038
12350
|
"CVE-2026-41091": {
|
|
12039
12351
|
"name": "Microsoft Defender (Malware Protection Engine) Link-Following LPE to SYSTEM",
|
|
12040
12352
|
"type": "LPE",
|
package/data/cwe-catalog.json
CHANGED
|
@@ -421,6 +421,7 @@
|
|
|
421
421
|
"hardening"
|
|
422
422
|
],
|
|
423
423
|
"evidence_cves": [
|
|
424
|
+
"CVE-2024-42479",
|
|
424
425
|
"CVE-2026-43284"
|
|
425
426
|
],
|
|
426
427
|
"framework_controls_partially_addressing": [
|
|
@@ -453,6 +454,7 @@
|
|
|
453
454
|
],
|
|
454
455
|
"evidence_cves": [
|
|
455
456
|
"CVE-2023-36424",
|
|
457
|
+
"CVE-2024-42478",
|
|
456
458
|
"CVE-2025-48633",
|
|
457
459
|
"CVE-2025-5419",
|
|
458
460
|
"CVE-2025-5777",
|
|
@@ -1589,6 +1591,7 @@
|
|
|
1589
1591
|
"CVE-2023-3519",
|
|
1590
1592
|
"CVE-2024-21762",
|
|
1591
1593
|
"CVE-2024-37079",
|
|
1594
|
+
"CVE-2024-42479",
|
|
1592
1595
|
"CVE-2025-14174",
|
|
1593
1596
|
"CVE-2025-14733",
|
|
1594
1597
|
"CVE-2025-21042",
|
|
@@ -2255,6 +2258,7 @@
|
|
|
2255
2258
|
"CVE-2025-6965",
|
|
2256
2259
|
"CVE-2025-7775",
|
|
2257
2260
|
"CVE-2026-20700",
|
|
2261
|
+
"CVE-2026-34159",
|
|
2258
2262
|
"CVE-2026-3910"
|
|
2259
2263
|
],
|
|
2260
2264
|
"last_verified": "2026-05-18",
|
|
@@ -36,6 +36,8 @@
|
|
|
36
36
|
"evidence_cves": [
|
|
37
37
|
"CVE-2023-48022",
|
|
38
38
|
"CVE-2024-0132",
|
|
39
|
+
"CVE-2024-42478",
|
|
40
|
+
"CVE-2024-42479",
|
|
39
41
|
"CVE-2024-50050",
|
|
40
42
|
"CVE-2025-1550",
|
|
41
43
|
"CVE-2025-23254",
|
|
@@ -57,6 +59,7 @@
|
|
|
57
59
|
"CVE-2026-30617",
|
|
58
60
|
"CVE-2026-30624",
|
|
59
61
|
"CVE-2026-30625",
|
|
62
|
+
"CVE-2026-34159",
|
|
60
63
|
"CVE-2026-40933"
|
|
61
64
|
],
|
|
62
65
|
"atlas_refs": [
|
|
@@ -1368,6 +1371,8 @@
|
|
|
1368
1371
|
"CVE-2024-27443",
|
|
1369
1372
|
"CVE-2024-37079",
|
|
1370
1373
|
"CVE-2024-42009",
|
|
1374
|
+
"CVE-2024-42478",
|
|
1375
|
+
"CVE-2024-42479",
|
|
1371
1376
|
"CVE-2024-43468",
|
|
1372
1377
|
"CVE-2024-50050",
|
|
1373
1378
|
"CVE-2024-54085",
|
|
@@ -1565,6 +1570,7 @@
|
|
|
1565
1570
|
"CVE-2026-32201",
|
|
1566
1571
|
"CVE-2026-33017",
|
|
1567
1572
|
"CVE-2026-33634",
|
|
1573
|
+
"CVE-2026-34159",
|
|
1568
1574
|
"CVE-2026-34197",
|
|
1569
1575
|
"CVE-2026-34621",
|
|
1570
1576
|
"CVE-2026-34926",
|
|
@@ -1763,6 +1769,8 @@
|
|
|
1763
1769
|
"evidence_cves": [
|
|
1764
1770
|
"CVE-2023-48022",
|
|
1765
1771
|
"CVE-2024-0132",
|
|
1772
|
+
"CVE-2024-42478",
|
|
1773
|
+
"CVE-2024-42479",
|
|
1766
1774
|
"CVE-2024-50050",
|
|
1767
1775
|
"CVE-2025-10585",
|
|
1768
1776
|
"CVE-2025-1094",
|
|
@@ -1791,6 +1799,7 @@
|
|
|
1791
1799
|
"CVE-2026-30624",
|
|
1792
1800
|
"CVE-2026-30625",
|
|
1793
1801
|
"CVE-2026-31431",
|
|
1802
|
+
"CVE-2026-34159",
|
|
1794
1803
|
"CVE-2026-34926",
|
|
1795
1804
|
"CVE-2026-39884",
|
|
1796
1805
|
"CVE-2026-40933",
|
|
@@ -2126,8 +2135,11 @@
|
|
|
2126
2135
|
"CVE-2023-48022",
|
|
2127
2136
|
"CVE-2024-0132",
|
|
2128
2137
|
"CVE-2024-40635",
|
|
2138
|
+
"CVE-2024-42478",
|
|
2139
|
+
"CVE-2024-42479",
|
|
2129
2140
|
"CVE-2025-23266",
|
|
2130
2141
|
"CVE-2025-53767",
|
|
2142
|
+
"CVE-2026-34159",
|
|
2131
2143
|
"CVE-2026-42897"
|
|
2132
2144
|
],
|
|
2133
2145
|
"atlas_refs": [
|
|
@@ -2351,6 +2363,8 @@
|
|
|
2351
2363
|
"CVE-2024-27443",
|
|
2352
2364
|
"CVE-2024-37079",
|
|
2353
2365
|
"CVE-2024-42009",
|
|
2366
|
+
"CVE-2024-42478",
|
|
2367
|
+
"CVE-2024-42479",
|
|
2354
2368
|
"CVE-2024-43468",
|
|
2355
2369
|
"CVE-2024-50050",
|
|
2356
2370
|
"CVE-2024-54085",
|
|
@@ -2558,6 +2572,7 @@
|
|
|
2558
2572
|
"CVE-2026-33017",
|
|
2559
2573
|
"CVE-2026-33634",
|
|
2560
2574
|
"CVE-2026-33825",
|
|
2575
|
+
"CVE-2026-34159",
|
|
2561
2576
|
"CVE-2026-34197",
|
|
2562
2577
|
"CVE-2026-34621",
|
|
2563
2578
|
"CVE-2026-34926",
|
|
@@ -4821,6 +4836,8 @@
|
|
|
4821
4836
|
"CVE-2023-48022",
|
|
4822
4837
|
"CVE-2024-0132",
|
|
4823
4838
|
"CVE-2024-21762",
|
|
4839
|
+
"CVE-2024-42478",
|
|
4840
|
+
"CVE-2024-42479",
|
|
4824
4841
|
"CVE-2024-50050",
|
|
4825
4842
|
"CVE-2025-1550",
|
|
4826
4843
|
"CVE-2025-23254",
|
|
@@ -4845,6 +4862,7 @@
|
|
|
4845
4862
|
"CVE-2026-30617",
|
|
4846
4863
|
"CVE-2026-30624",
|
|
4847
4864
|
"CVE-2026-30625",
|
|
4865
|
+
"CVE-2026-34159",
|
|
4848
4866
|
"CVE-2026-34926",
|
|
4849
4867
|
"CVE-2026-40933",
|
|
4850
4868
|
"CVE-2026-41091",
|
|
@@ -5341,6 +5359,8 @@
|
|
|
5341
5359
|
"evidence_cves": [
|
|
5342
5360
|
"CVE-2024-0132",
|
|
5343
5361
|
"CVE-2024-21762",
|
|
5362
|
+
"CVE-2024-42478",
|
|
5363
|
+
"CVE-2024-42479",
|
|
5344
5364
|
"CVE-2024-50050",
|
|
5345
5365
|
"CVE-2025-1550",
|
|
5346
5366
|
"CVE-2025-23254",
|
|
@@ -5361,6 +5381,7 @@
|
|
|
5361
5381
|
"CVE-2026-30617",
|
|
5362
5382
|
"CVE-2026-30624",
|
|
5363
5383
|
"CVE-2026-30625",
|
|
5384
|
+
"CVE-2026-34159",
|
|
5364
5385
|
"CVE-2026-34926",
|
|
5365
5386
|
"CVE-2026-40933",
|
|
5366
5387
|
"CVE-2026-41091",
|
|
@@ -5402,6 +5423,8 @@
|
|
|
5402
5423
|
"CVE-2023-48022",
|
|
5403
5424
|
"CVE-2024-0132",
|
|
5404
5425
|
"CVE-2024-21762",
|
|
5426
|
+
"CVE-2024-42478",
|
|
5427
|
+
"CVE-2024-42479",
|
|
5405
5428
|
"CVE-2024-50050",
|
|
5406
5429
|
"CVE-2025-1550",
|
|
5407
5430
|
"CVE-2025-23254",
|
|
@@ -5424,6 +5447,7 @@
|
|
|
5424
5447
|
"CVE-2026-30617",
|
|
5425
5448
|
"CVE-2026-30624",
|
|
5426
5449
|
"CVE-2026-30625",
|
|
5450
|
+
"CVE-2026-34159",
|
|
5427
5451
|
"CVE-2026-34926",
|
|
5428
5452
|
"CVE-2026-40933",
|
|
5429
5453
|
"CVE-2026-41091",
|