https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 22:15:25 +0000 https://cve.radiocsirt.org/vuln/cve-2025-59036 <p><strong>Affected:</strong> opsmill infrahub</p> <p>Infrahub offers a central hub to manage data, templates, and playbooks. Prior to versiond 1.3.9 and 1.4.5, a bug in the authentication logic will cause API tokens that were deleted and/or expired to be considered valid. This means that any API token that is associated with an active user account can authenticate successfully. This issue is fixed in versions 1.3.9 and 1.4.5. As a workaround, users can delete or deactivate the account associated with a deleted API token to prevent that token from authenticating.</p> <p><strong>Affected:</strong> opsmill infrahub</p> <p>Infrahub offers a central hub to manage data, templates, and playbooks. Prior to versiond 1.3.9 and 1.4.5, a bug in the authentication logic will cause API tokens that were deleted and/or expired to be considered valid. This means that any API token that is associated with an active user account can authenticate successfully. This issue is fixed in versions 1.3.9 and 1.4.5. As a workaround, users can delete or deactivate the account associated with a deleted API token to prevent that token from authenticating.</p> https://cve.radiocsirt.org/vuln/cve-2025-59036 https://cve.radiocsirt.org/vuln/ghsa-v2p7-4pv4-3wwh <p><strong>Affected:</strong> PyPI: infrahub-server</p> <p>### Impact A bug in the authentication logic will cause API tokens that were deleted and/or expired to be considered valid. This means that any API token that is associated with an active user account can authenticate successfully.</p> <p>### Patches This issue is fixed in versions `1.3.9` and `1.4.5`</p> <p>### Workarounds Users can delete or deactivate the account associated with a deleted API token to prevent that token from authenticating.</p> <p><strong>Affected:</strong> PyPI: infrahub-server</p> <p>### Impact A bug in the authentication logic will cause API tokens that were deleted and/or expired to be considered valid. This means that any API token that is associated with an active user account can authenticate successfully.</p> <p>### Patches This issue is fixed in versions `1.3.9` and `1.4.5`</p> <p>### Workarounds Users can delete or deactivate the account associated with a deleted API token to prevent that token from authenticating.</p> https://cve.radiocsirt.org/vuln/ghsa-v2p7-4pv4-3wwh