Ajenti version 2 contains an Information Disclosure vulnerability in Line 176 of the code source that can result in user and system enumera…

published 2018-03-13 8y ago modified 2026-06-17 4mo ago also PYSEC-2018-113 , EUVD-2018-0007

cvss: 7.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.6%; EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits: 0; none known

Ajenti version 2 contains an Information Disclosure vulnerability in Line 176 of the code source that can result in user and system enumeration as well as data from the /etc/ajenti/config.yml file. This attack appears to be exploitable via network connectivity to the web application.

Is CVE-2018-1000126 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

medium.com https://medium.com/stolabs/security-issues-on-ajenti-d2b7526eaeee referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	7.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
pypi	ajenti-panel	all versions	no fix listed

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

medium.com /stolabs/security-issues-on-ajenti-d2b7526eaeee
exploit, third-party-advisory, web
pypi.org /project/ajenti-panel
package
nvd.nist.gov /vuln/detail/CVE-2018-1000126
advisory

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.