CVE-2026-42576 — Any Workflow That Initializes The APK Database And Fetches R Vulnerability
CVE-2026-42576 — apko allows users to build and publish OCI container images built from apk packages. Prior to version 1.2.7, DiscoverKeys in pkg/apk/apk/implementation.go unconditionally type-asserts JWKS keys as *rsa.PublicKey without checking the key type. If a repository JWKS endpoint returns a
What This Means For You
- If your environment is affected by CWE-704, review your exposure and prioritize patching based on your environment. Monitor vendor advisories for CVE-2026-42576 updates and patches.
Related ATT&CK Techniques
🛡️ Detection Rules
2 rules · 6 SIEM formats2 detection rules auto-generated for this incident, mapped to MITRE ATT&CK. Sigma YAML is free — export to any SIEM format via the Intel Bot.
CVE-2026-42576 - Apko JWKS Type Assertion Panic
title: CVE-2026-42576 - Apko JWKS Type Assertion Panic
id: scw-2026-05-09-ai-1
status: experimental
level: high
description: |
Detects the execution of 'apko' with the 'init-apk-db' command, which is a precursor to the vulnerable JWKS key fetching process in apko versions prior to 1.2.7. This command, when followed by fetching repository keys, can trigger the panic due to unchecked type assertion of JWKS keys.
author: SCW Feed Engine (AI-generated)
date: 2026-05-09
references:
- https://shimiscyberworld.com/posts/nvd-CVE-2026-42576/
tags:
- attack.execution
- attack.t1204.002
logsource:
category: process_creation
detection:
selection:
Image|endswith:
- 'apko'
CommandLine|contains:
- 'init-apk-db'
condition: selection
falsepositives:
- Legitimate administrative activity
Source: Shimi's Cyber World · License & reuse
Indicators of Compromise
| ID | Type | Indicator |
|---|---|---|
| CVE-2026-42576 | vulnerability | CVE-2026-42576 |
| CWE-704 | weakness | CWE-704 |
Source & Attribution
| Source Platform | NVD |
| Channel | National Vulnerability Database |
| Published | May 09, 2026 at 23:16 UTC |
This content was curated and summarized by Shimi's Cyber World for informational purposes. It is not copied or republished in full. All intellectual property rights remain with the original author and source.
Believe this infringes your rights? Submit a takedown request.