# CVE-2026-12258: Inadequate access control in the Hiperdino REST API

> An attacker with a static bearer token can enumerate customer contact details via the public check endpoint, exposing personal information.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-jhq4-x77m-qmhx

## What is CVE-2026-12258?

CVE-2026-12258 is a critical vulnerability in Hiperdino REST API, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Inadequate access control in Hiperdino’s REST v1.0 API. The public endpoint ‘customer/check’ could allow an authenticated attacker to enter a telephone number or an email address. When the value entered belongs to a registered customer, the service returns the associated information (email address and telephone number). No authentication is required beyond a static bearer token, and there is no rate limiting or generic error handling. Successful exploitation of this vulnerability could allow a remote attacker to enumerate a user’s contact details, although this would require obtaining a valid static bearer token, constituting an information disclosure vulnerability.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-12258 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12258 is a critical vulnerability in Hiperdino REST API, published on 14 Sep 2026. 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-2026-12258 in the wild and no public exploit code.

Affected product: Hiperdino REST API. 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-12258/ (Markdown: https://insights.sbomify.com/CVE-2026-12258/index.md)
```

## Sources

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

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