Skip to main content
Vulnerability Database/CVE-2026-64945

CVE-2026-64945: Apache Answer Auth Bypass Vulnerability

CVE-2026-64945 is an authentication bypass flaw in Apache Answer allowing unauthorized question hide/show operations due to incorrect permission checks. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-64945 Overview

CVE-2026-64945 is a broken access control vulnerability in Apache Answer, an open-source Q&A platform. The flaw affects all versions through 2.0.2. The question operation controller evaluates the wrong permission when gating hide and show operations on questions. Instead of checking question.hide, the controller checks question.unpin, allowing users granted only the unpin permission to hide or restore questions. This issue [CWE-863] matters in deployments that use custom roles separating moderation permissions. Apache has released version 2.0.3 to address the flaw.

Critical Impact

Users with only question.unpin permission can hide or restore any question without holding question.hide or question.show, bypassing intended role boundaries in custom moderation configurations.

Affected Products

  • Apache Answer versions through 2.0.2
  • Deployments using custom role configurations that separate question.unpin, question.hide, and question.show permissions
  • Apache Answer 2.0.3 is the fixed release

Discovery Timeline

  • 2026-10-19 - CVE-2026-64945 published to the National Vulnerability Database
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-64945

Vulnerability Analysis

Apache Answer implements role-based access control over moderation actions on questions. These actions include pinning, unpinning, hiding, and restoring questions. Each action is intended to map to a discrete permission string such as question.pin, question.unpin, question.hide, and question.show.

The question operation controller handling hide and show requests evaluates the result of the question.unpin permission check rather than the question.hide or question.show check. The authorization decision is therefore based on the wrong input, even though the correct permission names exist elsewhere in the codebase.

In default deployments where moderators receive all of these permissions together, the flaw is not observable. In environments that assign question.unpin to a lower-privilege role, that role gains unintended ability to hide or restore any question.

Root Cause

The root cause is an incorrect authorization check [CWE-863]. The controller branches on the outcome of the unpin permission evaluation when deciding whether to execute hide or show operations. This is a logic error in permission wiring, not a missing check or an authentication flaw.

Attack Vector

An authenticated user holding a custom role that grants question.unpin but not question.hide or question.show can send normal hide or restore API requests through the Apache Answer interface. The backend accepts the request because the surrogate permission check succeeds. No crafted payloads, memory corruption, or injection techniques are required. Exploitation requires only valid session credentials and knowledge of the moderation endpoints exposed by the application.

See the Apache Security Mailing List Thread and the OpenWall OSS-Security Discussion for upstream details.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-64945

Indicators of Compromise

  • Questions appearing in a hidden or restored state without corresponding entries from accounts holding question.hide or question.show
  • Moderation audit log entries recording hide or show actions performed by users whose assigned role includes only question.unpin
  • Spikes in PUT or POST requests to question operation endpoints originating from non-moderator accounts

Detection Strategies

  • Review the Apache Answer role configuration and enumerate every custom role that grants question.unpin without also granting question.hide and question.show
  • Correlate web server access logs with application audit logs to identify hide or restore actions performed by accounts outside the moderator group
  • Query the database for recent changes to question visibility state and cross-reference the acting user against the expected permission set

Monitoring Recommendations

  • Enable verbose audit logging in Apache Answer for all moderation endpoints and forward logs to a central SIEM
  • Alert on moderation actions executed by accounts whose role does not nominally include hide or show privileges
  • Track creation and modification of custom roles that touch question-level permissions

How to Mitigate CVE-2026-64945

Immediate Actions Required

  • Upgrade Apache Answer to version 2.0.3 or later, which corrects the permission check in the question operation controller
  • Audit all custom roles and remove question.unpin from any role that should not also perform hide or restore operations until the upgrade is applied
  • Review recent moderation activity on hidden and restored questions and reverse any unauthorized state changes

Patch Information

The Apache Answer project has released version 2.0.3 to fix CVE-2026-64945. The fix corrects the controller to evaluate question.hide and question.show permissions against the respective operations. Administrators should follow the standard Apache Answer upgrade procedure and validate role assignments after the upgrade. Refer to the Apache Security Mailing List Thread for the official announcement.

Workarounds

  • Collapse the question.unpin, question.hide, and question.show permissions into a single moderator role so that users holding one also legitimately hold the others
  • Revoke question.unpin from any lower-privilege custom role until version 2.0.3 is deployed
  • Place Apache Answer moderation endpoints behind an upstream policy layer that enforces role-to-endpoint mapping independent of the application
bash
# Configuration example: identify custom roles granting question.unpin
# Run against the Apache Answer database (adjust table/column names to your schema)
SELECT r.id, r.name, p.permission_key
FROM role r
JOIN role_power_rel rp ON rp.role_id = r.id
JOIN power p ON p.id = rp.power_id
WHERE p.permission_key IN ('question.unpin', 'question.hide', 'question.show')
ORDER BY r.id;

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.