CVE-2026-58320: Apache Iggy: Snapshot API missing authorization
Missing Authorization vulnerability in the Apache Iggy server. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) checked only that the caller was logged in, not the readservers or manageservers permission. Any authenticated user, including a user with no permissions, could download a diagnostic archive with the server log files, the host process list, a file system listing and the runtime server configuration. The runtime configuration contains the HTTP JWT signing secret and the message encryption key when they are set in the configuration. If HTTP is enabled, the user could use the signing secret to create tokens for any account, including root.
This issue affects Apache Iggy: before 0.9.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.10.0
Event History
Frequently Asked Questions
Who can exploit this issue?
Any authenticated Apache Iggy user can request a system snapshot, including an account with no assigned permissions. The affected snapshot interfaces are GetSnapshot on binary transports and POST /snapshot on HTTP.
What information could an exposed snapshot reveal?
The diagnostic archive can contain server logs, the host process list, a file system listing, and the runtime server configuration. When configured, that runtime configuration includes the HTTP JWT signing secret and the message encryption key.
How could this lead to further compromise?
If HTTP is enabled and the JWT signing secret is present in the runtime configuration, an authenticated attacker could use it to create tokens for any account, including root. Access to the message encryption key may also expose encrypted message data.
Which deployments are affected and what is the remediation?
Apache Iggy versions before 0.9.0 are affected. Upgrade to version 0.10.0, which fixes the authorization issue.