Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-cc8m-98fm-rc9g | Skipper is vulnerable to arbitrary code execution through lua filters |
Wed, 18 Feb 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:zalando:skipper:*:*:*:*:*:*:*:* |
Mon, 19 Jan 2026 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Zalando
Zalando skipper |
|
| Vendors & Products |
Zalando
Zalando skipper |
Fri, 16 Jan 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 16 Jan 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Skipper is an HTTP router and reverse proxy for service composition. The default skipper configuration before 0.23.0 was -lua-sources=inline,file. The problem starts if untrusted users can create lua filters, because of -lua-sources=inline , for example through a Kubernetes Ingress resource. The configuration inline allows these user to create a script that is able to read the filesystem accessible to the skipper process and if the user has access to read the logs, they an read skipper secrets. This vulnerability is fixed in 0.23.0. | |
| Title | Skipper arbitrary code execution through lua filters | |
| Weaknesses | CWE-250 CWE-522 CWE-94 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-16T20:24:12.702Z
Reserved: 2026-01-15T15:45:01.958Z
Link: CVE-2026-23742
Updated: 2026-01-16T20:23:49.789Z
Status : Analyzed
Published: 2026-01-16T20:15:51.613
Modified: 2026-02-18T16:28:20.980
Link: CVE-2026-23742
No data.
OpenCVE Enrichment
Updated: 2026-04-18T05:45:38Z
Github GHSA