Skip to content
Applications

CVE-2026-63727

8.7
High
EPSS 0.26%Patch availableJul 29, 2026

Authenticated API privilege escalation in Anchore Enterprise (read→write permission escalation).

common questions

Is CVE-2026-63727 being exploited?

Not confirmed. CVE-2026-63727 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.

How severe is CVE-2026-63727?

CVE-2026-63727 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-63727?

Yes. A fix has been recorded for CVE-2026-63727. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-63727 affect?

CVE-2026-63727 affects Anchore Enterprise 5.11.0 - 5.27.1 (vulnerable), Anchore Enterprise 6.0.0 (vulnerable), Fixed in 5.27.2 and 6.0.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-63727?

Upgrade to 5.27.2 or 6.0.1; restrict API access, audit permissions, rotate creds.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Anchore Enterprise 5.11.0 - 5.27.1 (vulnerable)Anchore Enterprise 6.0.0 (vulnerable)Fixed in 5.27.2 and 6.0.1
impact

Authenticated attacker can modify user permissions via the user-management API to elevate read-only users to write access, enabling unauthorized changes to resources/operations.

action required

Immediate action required

affected versions
Anchore Anchore Enterprise
  • affected>= 5.11.0 and < 5.27.2
  • affected>= 6.0.0 and < 6.0.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free