/

CVE-2026-15319

Severity:

HIGH RISK

(7.3)

Improper Access Control (CWE-284) in PicoClaw Launcher

CVE-2026-15319

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-266, CWE-284

Impact:

Unauthorized Access and Policy Bypass

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Sipeed PicoClaw up to version 0.2.9 contains an improper access control flaw in the Launcher component's IPAllowlist middleware.

Under certain configurations, remote attackers may bypass intended IP-based restrictions and reach backend functionality that should be limited to trusted clients.

Affected context

The vulnerability manifests in deployments of Sipeed PicoClaw (≤ 0.2.9) where the Launcher component relies on the IPAllowlist middleware in web/backend/middleware/access_control.go to enforce network-based access control.

It is most relevant when operators assume that IP-based filtering alone sufficiently isolates administrative or sensitive routes.

The issue appears when the IP allowlist logic does not fully or correctly enforce the intended restrictions, creating gaps between configured policy and effective behavior.

Exploit preconditions

  • Attack surface: Network-accessible HTTP endpoints served by the Launcher back end.
  • Required access: Ability to send requests over the network to the PicoClaw web interface; no prior authentication is strictly required if the route relies primarily on IP-based controls.
  • Trigger point: Requests that should be gated or rejected based on the configured IP allowlist and associated access-control middleware.
  • Why exploitation is possible: The IPAllowlist implementation does not correctly enforce or interpret the administrator's policy, allowing clients from non-trusted IPs (or with crafted network characteristics) to access functionality that was assumed to be restricted.

Why this happens

The underlying issue is an improper access control design and implementation (CWE-284) in the IP allowlist middleware.

Instead of acting as a reliable gatekeeper, the middleware has logic flaws or incomplete validation that misclassify or mishandle client IPs.

This can stem from trusting mutable or ambiguous IP sources (e.g., headers, proxies), insufficient checks of address ranges, or failing to treat the allowlist as a strict deny-by-default policy.

Together with CWE-266 (Incorrect Privilege Assignment), this indicates that requests are effectively granted privileges that do not match their actual trust level, breaking the intended security boundary.

Potential impact

  • Remote clients may access administrative or internal-only endpoints that were assumed to be protected by IP restrictions.
  • Attackers could perform configuration changes or trigger sensitive operations intended only for trusted users.
  • Exposure of diagnostic or operational data that aids in further attacks.
  • Potential stepping stone for broader compromise of systems integrated with PicoClaw.

General mitigation guidance

Mitigation centers on aligning enforcement logic with intended policy and reducing reliance on IP-based trust boundaries.

Common patterns include:

  • Treating IP allowlists as a defense-in-depth layer rather than the sole control, and combining them with strong authentication and authorization checks.
  • Implementing clear deny-by-default semantics, ensuring that only explicitly listed addresses or subnets are permitted.
  • Normalizing and validating the true client IP source, avoiding direct trust in user-controlled headers and carefully handling reverse proxies.
  • Applying least-privilege principles so that backend endpoints expose only the minimal required functionality, even when accessed from trusted networks.
  • Centralizing access-control decisions so that policy is enforced consistently across routes and components.

How teams detect issues like this

Detection efforts can focus on both code-level and operational signals:

  • Static analysis for custom IP filtering logic that relies on headers (e.g., X-Forwarded-For) or performs incomplete range checks.
  • Code review checklists that flag bespoke access-control middleware and verify deny-by-default behavior, proper error handling, and clear logging for denied access.
  • Configuration reviews to ensure that reverse proxies, load balancers, and the application agree on the canonical client IP field.
  • Security testing and penetration testing that attempts to access restricted endpoints from untrusted networks or through proxy manipulation.
  • Use of automated policy-enforcement tools or WAF rules to detect anomalous access patterns to administrative routes.

Sources

SourceLink
github.comgithub.com/sipeed/picoclaw/
github.comgithub.com/sipeed/picoclaw/issues/3069
github.comgithub.com/sipeed/picoclaw/pull/3126
vuldb.comvuldb.com/cve/CVE-2026-15319
vuldb.comvuldb.com/submit/852884
vuldb.comvuldb.com/vuln/377259
vuldb.comvuldb.com/vuln/377259/cti

Frequently asked

questions

Yes. Because the Launcher's web interface is network-accessible, a remote attacker who can reach it over the network may attempt to bypass IP-based restrictions enforced by the IPAllowlist middleware.

An attacker generally needs only network-level access to the affected service.

They do not necessarily need valid credentials if sensitive routes depend primarily on IP allowlisting rather than strong authentication and authorization.

The safest pattern is to treat IP-based controls as supplemental, not primary, and to enforce strong authentication and fine-grained authorization on all sensitive routes.

Additionally, ensure the IP allowlist is implemented with strict deny-by-default semantics and uses a reliable source for client IP information.

Future prevention involves standardizing access-control mechanisms, avoiding ad hoc network trust checks, and subjecting them to rigorous review and testing.

Incorporate security design reviews for new middleware, apply least-privilege principles, and use automated checks or static analysis to flag custom access-control code for closer scrutiny.

Find out what's already
exploitable in your codebase.