Is ansibleguy-webui safe to use?

Vulert records 2 vulnerabilities for ansibleguy-webui in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is ansibleguy-webui's Vulert package health score?

Vulert scores ansibleguy-webui 67/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of ansibleguy-webui affected?

No. 0.0.25, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of ansibleguy-webui should I use?

0.0.25 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does ansibleguy-webui have?

2 vulnerabilities are recorded for ansibleguy-webui in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ansibleguy-webui vulnerabilities disclosed?

1 vulnerability was recorded for ansibleguy-webui in the last 12 months, and the oldest entry in this database dates to 28 May 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of ansibleguy-webui are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor ansibleguy-webui for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at https://vulert.com/scanner and Vulert keeps checking the ansibleguy-webui version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.

Vulnerability Database · PyPI · Package report

ansibleguy-webui: vulnerability history, versions and safety

ansibleguy-webui is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 6 releases, from May 2024 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

2 vulnerabilities recorded H1 U1

0 with no fix published

Every vulnerability has a patched version to move to.

1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ansibleguy-webui vulnerabilities

Vulert verdict on ansibleguy-webui 0.0.25 i

Updated on 23 Oct 2026

Good news: 0.0.25, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 67/100

Security Minor issues
Maintenance Maintaining
Popularity Little adoption
Community Not enough data

What to do: Stay on 0.0.25 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.0.25 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

Current release 0.0.25 — unaffected i
Vulnerabilities on record 2 over 2 years · 1 in the last year i
Latest disclosure 07 Jul 2026 i
Highest CVSS 8.2 i
With no published fix 0 i
Last release 21 months ago i
Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for ansibleguy-webui, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
0.0.25	21 Jan 2025	none	non-standard	—	Details →
0.0.24.post3	06 Oct 2024	none	non-standard	—	Details →
0.0.24.post2	05 Oct 2024	none	non-standard	—	Details →
0.0.24	27 Sep 2024	none	non-standard	—	Details →
0.0.23.post3	20 Jul 2024	none	non-standard	—	Details →
0.0.22.post2	13 Jul 2024	none	non-standard	—	Details →
0.0.21.post2	20 May 2024	none	non-standard	—	Details →
0.0.20	13 May 2024	H1 U1	non-standard	Yes	Details →
0.0.19	12 May 2024	H1 U1	non-standard	Yes	Details →
0.0.18	15 Mar 2024	H1 U1	non-standard	Yes	Details →
0.0.17	09 Mar 2024	H1 U1	non-standard	Yes	Details →
0.0.16	07 Mar 2024	H1 U1	non-standard	Yes	Details →
0.0.15	03 Mar 2024	H1 U1	non-standard	Yes	Details →

All 13 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

2024 1
2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 2 were recorded in the last 12 months.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for ansibleguy-webui

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CVE-2024-36110: ansibleguy-webui Cross-site Scripting vulnerability	8.2 high	0.0.21	28 May 2024
CVE-2024-36110: ansibleguy-webui Cross-site Scripting Vulnerability	8.2 high	0.0.21	07 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315