Use of Hard-coded Credentials in drEryk Gabinet

Answer in brief

CVE-2026-17038 records a Unknown severity vulnerability in Use of Hard-coded Credentials in drEryk Gabinet. The current sources do not mark it as known exploited. The current feed maps drEryk/drEryk Gabinet (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 10, 2026Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps drEryk/drEryk Gabinet (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
drEryk/drEryk Gabinetgeneric	>=0 <11.5.0	11.5.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for drEryk/drEryk Gabinet.
Review the reported fix. Update drEryk/drEryk Gabinet to 11.5.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.