OpenClaw LINE EUVD-2026-87485

Requires the OpenClaw LINE integration configured in group allowlist mode with the groupAllowFrom option left unset, combined with a DM allowFrom value that is broader than the intended group access - the vulnerability is the silent fallback of group authorization to DM allowFrom. The attacker must also be a participant in a LINE group that the bot is a member of in order to send the triggering message. Deployments that explicitly configure groupAllowFrom, or whose DM allowFrom is no broader than intended group access, are not exposed; this is a misconfiguration-dependent flaw rather than a default-state remote break.

This is a genuine but low-severity access-control weakness, not a high-priority emergency. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N) yields 6.9 (Medium) driven entirely by the network vector and low complexity; actual technical impact is capped at Low confidentiality and Low integrity with no availability effect, so the score overstates real danger. There is no EPSS score, no CISA KEV listing, and no public exploit code in the provided intelligence, so exploitation status is 'no public exploit identified at time of analysis' - no evidence of active or automatable exploitation. The PR:N rating warrants scrutiny: the flaw requires the attacker to already be a participant in a LINE group the bot is in, which is a real-world precondition even if it is not application-level authentication, so raw AV:N/PR:N understates the group-membership gate. Critically this is a configuration-inheritance bug: it only manifests when an operator sets group allowlist mode but leaves groupAllowFrom unset AND has a broader DM allowFrom - a specific misconfiguration, not a universally exploitable default. Net: a real correctness/authorization defect worth patching, but low real-world risk absent the enabling misconfiguration.

An operator deploys the OpenClaw LINE agent, restricting group triggering via allowlist mode but never explicitly setting groupAllowFrom, while leaving DM allowFrom broad. An attacker who is (or joins) a group the bot participates in sends a triggering message; because group authorization silently falls back to the broader DM allowFrom list, the agent responds despite the intended group restriction. No public exploit code is known, and the attack requires only ordinary group participation and a crafted message.