# CVE-2026-17038: Use of Hard-coded Credentials in drEryk Gabinet

> Hard-coded API credentials in drEryk Gabinet allow attackers to authenticate and perform privileged ticket operations.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/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:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-4qc3-v5c2-6x2v

## What is CVE-2026-17038?

CVE-2026-17038 is a medium-severity vulnerability in drEryk Gabinet, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DrEryk Gabinet before 11.5.0 uses hard-coded API credentials in its ticket reporting component. These credentials can be used to authenticate directly to the ticket system API. This allows an attacker to perform privileged operations beyond what is offered by the application, including reading and modifying tickets.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-17038 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17038 is a medium-severity vulnerability in drEryk Gabinet, published on 10 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-17038 in the wild and no public exploit code.

Affected product: drEryk Gabinet. 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-17038/ (Markdown: https://insights.sbomify.com/CVE-2026-17038/index.md)
```

## Sources

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

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