Skip to content
Fencer Intel
medium 5.2

CVE-2025-24882 json

regclient may ignore pinned manifest digests

published 2y ago modified last mo. also GHSA-qv35-3gw6-8q4j , GO-2024-3038 , EUVD-2024-2641

cvss
5.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

regclient is a Docker and OCI Registry Client in Go. A malicious registry could return a different digest for a pinned manifest without detection. This vulnerability is fixed in 0.7.1.

Patch / fix

  • go github.com/regclient/regclient 0.7.1

Is CVE-2025-24882 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-24882 updated cvss 5.2

regclient: Pinned manifest digests may be ignored

  • Red Hat Trusted Profile Analyzer trustification-guac
    affected: workaround, no fix available “Red Hat Product Security has not identified any applicable mitigations at this time.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:N
GitHub 3.1 5.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/regclient/regclient
<0.7.1
0.7.1

Affected products

  • regclient regclient

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-345 Insufficient Verification of Data Authenticity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.