Lookup for vulnerable packages by Package URL.
| Purl | pkg:apk/alpine/mbedtls@3.6.4-r0?arch=ppc64le&distroversion=v3.20&reponame=main |
| Type | apk |
| Namespace | alpine |
| Name | mbedtls |
| Version | 3.6.4-r0 |
| Qualifiers |
| arch |
ppc64le |
| distroversion |
v3.20 |
| reponame |
main |
|
| Subpath | |
| Is_vulnerable | false |
| Next_non_vulnerable_version | 3.6.5-r0 |
| Latest_non_vulnerable_version | 3.6.6-r0 |
| Affected_by_vulnerabilities |
|
| Fixing_vulnerabilities |
| 0 |
| url |
VCID-2xan-jnv1-x3f5 |
| vulnerability_id |
VCID-2xan-jnv1-x3f5 |
| summary |
In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_import_public_key does not check that the input buffer is at least 4 bytes before reading a 32-bit field, allowing a possible out-of-bounds read on truncated input. Specifically, an out-of-bounds read in mbedtls_lms_import_public_key allows context-dependent attackers to trigger a crash or limited adjacent-memory disclosure by supplying a truncated LMS (Leighton-Micali Signature) public-key buffer under four bytes. An LMS public key starts with a 4-byte type indicator. The function mbedtls_lms_import_public_key reads this type indicator before validating the size of its input. |
| references |
| 0 |
| reference_url |
https://api.first.org/data/v1/epss?cve=CVE-2025-49601 |
| reference_id |
|
| reference_type |
|
| scores |
| 0 |
| value |
0.00255 |
| scoring_system |
epss |
| scoring_elements |
0.49086 |
| published_at |
2026-06-06T12:55:00Z |
|
| 1 |
| value |
0.00255 |
| scoring_system |
epss |
| scoring_elements |
0.49039 |
| published_at |
2026-06-08T12:55:00Z |
|
| 2 |
| value |
0.00255 |
| scoring_system |
epss |
| scoring_elements |
0.49052 |
| published_at |
2026-06-09T12:55:00Z |
|
| 3 |
| value |
0.00255 |
| scoring_system |
epss |
| scoring_elements |
0.49076 |
| published_at |
2026-06-05T12:55:00Z |
|
| 4 |
| value |
0.00255 |
| scoring_system |
epss |
| scoring_elements |
0.49069 |
| published_at |
2026-06-07T12:55:00Z |
|
|
| url |
https://api.first.org/data/v1/epss?cve=CVE-2025-49601 |
|
| 1 |
|
| 2 |
|
|
| fixed_packages |
|
| aliases |
CVE-2025-49601
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-2xan-jnv1-x3f5 |
|
| 1 |
| url |
VCID-334y-58us-d7cg |
| vulnerability_id |
VCID-334y-58us-d7cg |
| summary |
Mbed TLS before 3.6.4 has a race condition in AESNI detection if certain compiler optimizations occur. An attacker may be able to extract an AES key from a multithreaded program, or perform a GCM forgery. |
| references |
| 0 |
| reference_url |
https://api.first.org/data/v1/epss?cve=CVE-2025-52496 |
| reference_id |
|
| reference_type |
|
| scores |
| 0 |
| value |
0.00085 |
| scoring_system |
epss |
| scoring_elements |
0.24793 |
| published_at |
2026-06-06T12:55:00Z |
|
| 1 |
| value |
0.00085 |
| scoring_system |
epss |
| scoring_elements |
0.24677 |
| published_at |
2026-06-08T12:55:00Z |
|
| 2 |
| value |
0.00085 |
| scoring_system |
epss |
| scoring_elements |
0.24686 |
| published_at |
2026-06-09T12:55:00Z |
|
| 3 |
| value |
0.00085 |
| scoring_system |
epss |
| scoring_elements |
0.24804 |
| published_at |
2026-06-05T12:55:00Z |
|
| 4 |
| value |
0.00085 |
| scoring_system |
epss |
| scoring_elements |
0.24735 |
| published_at |
2026-06-07T12:55:00Z |
|
|
| url |
https://api.first.org/data/v1/epss?cve=CVE-2025-52496 |
|
| 1 |
|
| 2 |
|
| 3 |
|
| 4 |
|
|
| fixed_packages |
|
| aliases |
CVE-2025-52496
|
| risk_score |
3.5 |
| exploitability |
0.5 |
| weighted_severity |
7.0 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-334y-58us-d7cg |
|
| 2 |
| url |
VCID-6eka-6yut-s3hj |
| vulnerability_id |
VCID-6eka-6yut-s3hj |
| summary |
In Mbed TLS 3.6.1 through 3.6.3 before 3.6.4, a timing discrepancy in block cipher padding removal allows an attacker to recover the plaintext when PKCS#7 padding mode is used. |
| references |
| 0 |
| reference_url |
https://api.first.org/data/v1/epss?cve=CVE-2025-49087 |
| reference_id |
|
| reference_type |
|
| scores |
| 0 |
| value |
0.00428 |
| scoring_system |
epss |
| scoring_elements |
0.62813 |
| published_at |
2026-06-08T12:55:00Z |
|
| 1 |
| value |
0.00428 |
| scoring_system |
epss |
| scoring_elements |
0.62828 |
| published_at |
2026-06-05T12:55:00Z |
|
| 2 |
| value |
0.00428 |
| scoring_system |
epss |
| scoring_elements |
0.62837 |
| published_at |
2026-06-06T12:55:00Z |
|
| 3 |
| value |
0.00428 |
| scoring_system |
epss |
| scoring_elements |
0.62827 |
| published_at |
2026-06-09T12:55:00Z |
|
|
| url |
https://api.first.org/data/v1/epss?cve=CVE-2025-49087 |
|
| 1 |
|
| 2 |
|
| 3 |
|
|
| fixed_packages |
|
| aliases |
CVE-2025-49087
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-6eka-6yut-s3hj |
|
| 3 |
| url |
VCID-a267-c94c-y7e3 |
| vulnerability_id |
VCID-a267-c94c-y7e3 |
| summary |
Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation. The function mbedtls_x509_string_to_names() takes a head argument that is documented as an output argument. The documentation does not suggest that the function will free that pointer; however, the function does call mbedtls_asn1_free_named_data_list() on that argument, which performs a deep free(). As a result, application code that uses this function (relying only on documented behavior) is likely to still hold pointers to the memory blocks that were freed, resulting in a high risk of use-after-free or double-free. In particular, the two sample programs x509/cert_write and x509/cert_req are affected (use-after-free if the san string contains more than one DN). |
| references |
| 0 |
| reference_url |
https://api.first.org/data/v1/epss?cve=CVE-2025-47917 |
| reference_id |
|
| reference_type |
|
| scores |
| 0 |
| value |
0.0843 |
| scoring_system |
epss |
| scoring_elements |
0.92504 |
| published_at |
2026-06-09T12:55:00Z |
|
| 1 |
| value |
0.0843 |
| scoring_system |
epss |
| scoring_elements |
0.92496 |
| published_at |
2026-06-05T12:55:00Z |
|
| 2 |
| value |
0.0843 |
| scoring_system |
epss |
| scoring_elements |
0.92491 |
| published_at |
2026-06-06T12:55:00Z |
|
| 3 |
| value |
0.0843 |
| scoring_system |
epss |
| scoring_elements |
0.92486 |
| published_at |
2026-06-07T12:55:00Z |
|
| 4 |
| value |
0.0843 |
| scoring_system |
epss |
| scoring_elements |
0.92485 |
| published_at |
2026-06-08T12:55:00Z |
|
|
| url |
https://api.first.org/data/v1/epss?cve=CVE-2025-47917 |
|
| 1 |
|
| 2 |
|
| 3 |
|
| 4 |
|
| 5 |
|
| 6 |
|
|
| fixed_packages |
|
| aliases |
CVE-2025-47917
|
| risk_score |
10.0 |
| exploitability |
2.0 |
| weighted_severity |
8.0 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-a267-c94c-y7e3 |
|
| 4 |
| url |
VCID-emw2-7ad4-9bcm |
| vulnerability_id |
VCID-emw2-7ad4-9bcm |
| summary |
Mbed TLS before 3.6.4 has a NULL pointer dereference because mbedtls_asn1_store_named_data can trigger conflicting data with val.p of NULL but val.len greater than zero. |
| references |
| 0 |
| reference_url |
https://api.first.org/data/v1/epss?cve=CVE-2025-48965 |
| reference_id |
|
| reference_type |
|
| scores |
| 0 |
| value |
0.00196 |
| scoring_system |
epss |
| scoring_elements |
0.4142 |
| published_at |
2026-06-09T12:55:00Z |
|
| 1 |
| value |
0.00196 |
| scoring_system |
epss |
| scoring_elements |
0.41466 |
| published_at |
2026-06-05T12:55:00Z |
|
| 2 |
| value |
0.00196 |
| scoring_system |
epss |
| scoring_elements |
0.41471 |
| published_at |
2026-06-06T12:55:00Z |
|
| 3 |
| value |
0.00196 |
| scoring_system |
epss |
| scoring_elements |
0.4144 |
| published_at |
2026-06-07T12:55:00Z |
|
| 4 |
| value |
0.00196 |
| scoring_system |
epss |
| scoring_elements |
0.41409 |
| published_at |
2026-06-08T12:55:00Z |
|
|
| url |
https://api.first.org/data/v1/epss?cve=CVE-2025-48965 |
|
| 1 |
|
| 2 |
|
| 3 |
|
| 4 |
|
| 5 |
|
|
| fixed_packages |
|
| aliases |
CVE-2025-48965
|
| risk_score |
1.8 |
| exploitability |
0.5 |
| weighted_severity |
3.6 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-emw2-7ad4-9bcm |
|
| 5 |
| url |
VCID-smuy-m4tp-7ud2 |
| vulnerability_id |
VCID-smuy-m4tp-7ud2 |
| summary |
Mbed TLS before 3.6.4 has a PEM parsing one-byte heap-based buffer underflow, in mbedtls_pem_read_buffer and two mbedtls_pk_parse functions, via untrusted PEM input. |
| references |
| 0 |
| reference_url |
https://api.first.org/data/v1/epss?cve=CVE-2025-52497 |
| reference_id |
|
| reference_type |
|
| scores |
| 0 |
| value |
0.00365 |
| scoring_system |
epss |
| scoring_elements |
0.58827 |
| published_at |
2026-06-05T12:55:00Z |
|
| 1 |
| value |
0.00365 |
| scoring_system |
epss |
| scoring_elements |
0.58833 |
| published_at |
2026-06-06T12:55:00Z |
|
| 2 |
| value |
0.00365 |
| scoring_system |
epss |
| scoring_elements |
0.58826 |
| published_at |
2026-06-09T12:55:00Z |
|
| 3 |
| value |
0.00365 |
| scoring_system |
epss |
| scoring_elements |
0.58811 |
| published_at |
2026-06-08T12:55:00Z |
|
|
| url |
https://api.first.org/data/v1/epss?cve=CVE-2025-52497 |
|
| 1 |
|
| 2 |
|
| 3 |
|
| 4 |
|
|
| fixed_packages |
|
| aliases |
CVE-2025-52497
|
| risk_score |
2.1 |
| exploitability |
0.5 |
| weighted_severity |
4.3 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-smuy-m4tp-7ud2 |
|
| 6 |
| url |
VCID-uzkr-v91c-kkbp |
| vulnerability_id |
VCID-uzkr-v91c-kkbp |
| summary |
In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. Specifically, unchecked return values in mbedtls_lms_verify allow an attacker (who can induce a hardware hash accelerator fault) to bypass LMS signature verification by reusing stale stack data, resulting in acceptance of an invalid signature. In mbedtls_lms_verify, the return values of the internal Merkle tree functions create_merkle_leaf_value and create_merkle_internal_value are not checked. These functions return an integer that indicates whether the call succeeded or not. If a failure occurs, the output buffer (Tc_candidate_root_node) may remain uninitialized, and the result of the signature verification is unpredictable. When the software implementation of SHA-256 is used, these functions will not fail. However, with hardware-accelerated hashing, an attacker could use fault injection against the accelerator to bypass verification. |
| references |
| 0 |
| reference_url |
https://api.first.org/data/v1/epss?cve=CVE-2025-49600 |
| reference_id |
|
| reference_type |
|
| scores |
| 0 |
| value |
0.00046 |
| scoring_system |
epss |
| scoring_elements |
0.14718 |
| published_at |
2026-06-06T12:55:00Z |
|
| 1 |
| value |
0.00046 |
| scoring_system |
epss |
| scoring_elements |
0.14593 |
| published_at |
2026-06-08T12:55:00Z |
|
| 2 |
| value |
0.00046 |
| scoring_system |
epss |
| scoring_elements |
0.14617 |
| published_at |
2026-06-09T12:55:00Z |
|
| 3 |
| value |
0.00046 |
| scoring_system |
epss |
| scoring_elements |
0.14712 |
| published_at |
2026-06-05T12:55:00Z |
|
| 4 |
| value |
0.00046 |
| scoring_system |
epss |
| scoring_elements |
0.14676 |
| published_at |
2026-06-07T12:55:00Z |
|
|
| url |
https://api.first.org/data/v1/epss?cve=CVE-2025-49600 |
|
| 1 |
|
| 2 |
|
|
| fixed_packages |
|
| aliases |
CVE-2025-49600
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-uzkr-v91c-kkbp |
|
|
| Risk_score | null |
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:apk/alpine/mbedtls@3.6.4-r0%3Farch=ppc64le&distroversion=v3.20&reponame=main |