# CVE-2025-56332: Auth bypass in n/a

> Attackers can bypass authentication to access Pangolin resources due to insecure default configurations.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Dec 2025
- **Updated:** 2 Jan 2026
- **Also known as:** GHSA-3p4c-m632-jv39

## What is CVE-2025-56332?

CVE-2025-56332 is a critical authentication bypass vulnerability in n/a, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication Bypass in fosrl/pangolin v1.6.2 and before allows attackers to access Pangolin resource via Insecure Default Configuration

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2025-56332?

It affects 1 product.


Products: Pangolin Pangolin.

## How do I fix CVE-2025-56332?

No fix has been published for CVE-2025-56332 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-56332 being exploited?

There is no known exploitation of CVE-2025-56332 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-56333](https://insights.sbomify.com/CVE-2025-56333/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-56332 and fix it if it is affected.

What it is: CVE-2025-56332 is a critical authentication bypass vulnerability in n/a, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-56332 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-56332/ (Markdown: https://insights.sbomify.com/CVE-2025-56332/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-56332
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-56332
- OSV: https://osv.dev/vulnerability/CVE-2025-56332

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-56332/
Summaries are generated and may contain mistakes; the official description above is the record.