# CVE-2026-31278: Information disclosure in BioStar 2

> Attackers can obtain Active Directory service account credentials in cleartext via a crafted GET request to the adserver setting endpoint.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-h5qg-wfw7-j3ph

## What is CVE-2026-31278?

CVE-2026-31278 is a high-severity vulnerability in supremainc BioStar 2, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue in the /api/v2/setting/adserversetting endpoint of Suprema BioStar 2 before 2.9.12 and and BioStar X before 1.0.2 allows attackers to obtain Active Directory service account credentials in cleartext by supplying a crafted GET request.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2026-31278?


## How do I fix CVE-2026-31278?

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

## Is CVE-2026-31278 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31278 exists.

Public exploit code:

- CVE write-up for Active Directory credential exposure vulnerability in Suprema BioStar 2 (github_poc): https://github.com/mda1r/CVE-2026-31278

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-31278 and fix it if it is affected.

What it is: CVE-2026-31278 is a high-severity vulnerability in supremainc BioStar 2, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31278 exists.

Affected product: supremainc BioStar 2. 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-2026-31278/ (Markdown: https://insights.sbomify.com/CVE-2026-31278/index.md)
```

## Sources

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

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