CVE-2026-64858: vulnerability-operator: IDOR exposing vulnerability reports via unauthenticated Report Handler

Published Nov 11, 2026
·
Updated

vulnerability-operator scans SBOMs and Images for vulnerabilities. Prior to version 0.28.16, an unauthenticated information-disclosure vulnerability exposes all vulnerability scan reports served by the operator. The /report/ HTTP endpoint mounts a raw http.FileServer over the reports directory (default /reports) with no authentication, authorization, or middleware. Any client that can reach the operator's HTTP port (default 8080) can list and download every JSON vulnerability report, disclosing CVE IDs, affected package names/versions, and container image identifiers for every workload scanned in the cluster. This issue has been patched in version 0.28.16.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade vulnerability-operator to a version that resolves this vulnerability.

    Fixed in 0.28.16

Event History

Nov 11, 2026
CVE Published
via MITRE·05:45 PM
Data Sourced
via MITRE·05:45 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:19 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can access the exposed reports?

Any unauthenticated client that can reach the operator's HTTP port can list and download all reports. The default HTTP port is 8080, so exposure depends on whether that port is reachable from the client's network location.

2

Are default deployments affected?

Yes. Before version 0.28.16, the /report/ endpoint serves the reports directory without authentication or authorization. The default reports directory is /reports.

3

What information can be disclosed?

An attacker can retrieve JSON vulnerability reports for every workload scanned in the cluster. These reports can disclose CVE IDs, affected package names and versions, and container image identifiers.

4

What should be done if an immediate upgrade is not possible?

Restrict network access to the operator's HTTP port so untrusted clients cannot reach it. This limits access to the unauthenticated /report/ endpoint until version 0.28.16 can be deployed.

5

How can I determine whether reports may already be exposed?

Check whether the deployment runs a version earlier than 0.28.16 and whether its HTTP port, default 8080, is reachable by untrusted clients. If both conditions apply, the reports served from /report/ may have been accessible without authentication.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203