Pig before 4.1.2 Missing Authorization Exposes OAuth2 Client Secrets via /client
Affects Pig versions before 4.1.2, where an authenticated user without client-management permission can read OAuth2 client secrets. Fixed in 4.1.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.1.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Pig versions before 4.1.2
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Pig before 4.1.2 contains a missing authorization vulnerability in SysClientController that allows authenticated users without client-management permission to retrieve OAuth2 client secrets via GET /client/{clientId} and GET /client/export. Attackers can fetch clientSecret values for seed clients like pig, app, and daemon or export the client table, then obtain tokens using those clients' configured grant types.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Pig versions before 4.1.2Upgrade to a fixed version: 4.1.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- pig-mesh pig
fixed in 4.1.2
Evidence 6
- Patch
- Report
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125377
Is CVE-2026-125377 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The /client endpoints do not check permissions properly, so an logged-in user who lacks client-management rights can read OAuth2 client secrets, including those of seed clients such as pig, app and daemon, and export the whole client table. With those secrets the user can request tokens using the grant types those clients are configured for.Source: vulncheck.com
Which versions are affected by CVE-2026-125377?
pig: before 4.1.2.Source: cve.now feed data
Am I affected, and how do I check?
Pig versions before 4.1.2 are affected. To check a deployment, look at the Pig version in use and confirm whether it is earlier than 4.1.2; the vulnerable endpoints are GET /client/{clientId} and GET /client/export.Source: vulncheck.com
How do I fix CVE-2026-125377?
Upgrade Pig to version 4.1.2 or later, which contains the fix.Source: vulncheck.com