- Exploited
- No known exploitation
- Fix
- Fixed in 0.9.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.9.0.
Summary
Apache Iggy's snapshot command failed to check the read_servers or manage_servers permission, so any logged-in user, even one with no permissions, could download a diagnostic archive. The archive includes server logs, the process list, a file listing, and the runtime configuration, which can expose the HTTP JWT signing secret and message encryption key; with HTTP enabled, that secret can be used to forge tokens for any account, including root.
Original description
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 read_servers or manage_servers 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.9.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-58320 (Apache Iggy: Snapshot API missing authorization), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-58320 (entry last updated 2026-11-18):
Affected:
- Apache Software Foundation Apache Iggy: fixed in 0.9.0
Fixed versions: 0.9.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-58320 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-58320 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/39ymot2srv5wnopxmfxy28tvzjgcqdnq
- https://github.com/apache/iggy/pull/3579
- http://www.openwall.com/lists/oss-security/2026/11/17/28
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-58320
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-58320"}.Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- apache/iggy
fixed in 0.9.0
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | lists.apache.org · thread/39ymot2srv5wnopxmfxy28tvzjgcqdnq |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-58320 |
| Record | NVD · CVE-2026-58320 |
| Write-ups 1Establishes: Technical detail and context. | |
| Link | openwall.com · lists/oss-security/2026/11/17/28 |
| Other links 1 | |
| Patch | GitHub · apache/iggy · Pull request #3579 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-58320
Is CVE-2026-58320 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-58320?
apache/iggy: before 0.9.0.Source: cve.now feed data
How do I fix CVE-2026-58320?
Upgrade to a fixed version: 0.9.0.Source: cve.now feed data