chainguard-dev apko up to 1.2.6 JWKS Endpoint implementation.go type conversion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in chainguard-dev apko up to 1.2.6. It has been classified as problematic. This issue affects some unknown processing of the file pkg/apk/apk/implementation.go of the component JWKS Endpoint. The manipulation leads to type conversion. This vulnerability is referenced as CVE-2026-42576. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in chainguard-dev apko up to 1.2.6. It has been rated as problematic. This issue affects an unknown code block of the file pkg/apk/apk/implementation.go of the component JWKS Endpoint. The manipulation with an unknown input leads to a type conversion vulnerability. Using CWE to declare the problem leads to CWE-704. The product does not correctly convert an object, resource, or structure from one type to a different type. Impacted is availability. The summary by CVE is:
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 non-RSA key (e.g. EC), the unchecked assertion panics and crashes apko. This affects any workflow that initializes the APK database and fetches repository keys. This issue has been patched in version 1.2.7.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-42576 since 04/28/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 1.2.7 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 6604826b19e36e9bc6e196592800fad93738f4a1 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Type conversionCWE: CWE-704
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: apko 1.2.7
Patch: 6604826b19e36e9bc6e196592800fad93738f4a1
Timeline
04/28/2026 CVE reserved05/10/2026 Advisory disclosed
05/10/2026 VulDB entry created
05/10/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-m7hm-vm4x-28jf
Status: Confirmed
CVE: CVE-2026-42576 (🔒)
GCVE (CVE): GCVE-0-2026-42576
GCVE (VulDB): GCVE-100-362465
Entry
Created: 05/10/2026 08:46Changes: 05/10/2026 08:46 (68)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.