dbcve.org
HelixApplication · Apache

CVE-2026-57111

HIGH · 7.5 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 2.0.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Permissive Cross-Origin Resource Sharing (CORS) in the REST API (helix-rest, org.apache.helix.rest.server.filters.CORSFilter) in Apache Helix through 2.0.0 on all platforms allows a remote attacker controlling a web page visited by an authorized user to read responses from and issue cross-origin requests to administrative REST endpoints via a cross-origin request from an arbitrary origin, since the filter unconditionally returns Access-Control-Allow-Origin: * together with Access-Control-Allow-Credentials: true and reflects arbitrary Access-Control-Request-Method / Access-Control-Request-Headers values in preflight responses. Users are recommended to upgrade to version 2.0.1, which fixes this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Helix REST API CORS filter allows unrestricted cross-origin access by returning Access-Control-Allow-Origin: * with Access-Control-Allow-Credentials: true, and blindly reflects arbitrary Access-Control-Request-Method/Headers values. This enables remote attackers to make authenticated cross-origin requests to administrative REST endpoints from malicious web pages.

MitigationUpgrade to Apache Helix version 2.0.1 which implements proper CORS origin validation and restricts credentialed requests to explicitly allowed origins.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HelixApplication
Affected:< 2.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Helix installation and version
    Locate the Apache Helix installation or JAR files and determine the version. Common methods: check the build configuration (pom.xml), JAR manifest, or run 'grep -r "helix" version' in the installation directory.
    Affected if The installed version is lower than 2.0.1 (e.g., 2.0.0, 1.x.x, or any version number less than 2.0.1).
  2. Determine if the REST API is enabled
    Check your Helix configuration for REST API enablement. Look for settings like 'helix.rest.enabled=true' or similar in your cluster configuration files or property files.
    Affected if The REST API is enabled and exposed on a network-accessible endpoint.
  3. Inspect the CORS filter configuration
    Examine the CORS configuration for the REST API endpoints. Look for Access-Control-Allow-Origin, Access-Control-Allow-Credentials, and Access-Control-Request-Method/Headers settings in the web.xml, filter configuration, or Helix property files.
    Affected if The configuration shows Access-Control-Allow-Origin is set to '*' (wildcard) while Access-Control-Allow-Credentials is set to 'true', or if Access-Control-Request-Method/Headers values are reflected without validation.

You are affected if your Apache Helix version is below 2.0.1 AND the REST API is enabled with the insecure CORS configuration (wildcard origin with credentials allowed, or arbitrary method/header reflection).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.1 or later
Fixed in 2.0.1
Interim mitigation

Upgrade to Apache Helix version 2.0.1 which implements proper CORS origin validation and restricts credentialed requests to explicitly allowed origins.

Recommended fix High confidence

Apache Helix 2.0.1

  1. Identify the current Apache Helix version in use by checking the project dependencies or JAR file version
  2. Download Apache Helix version 2.0.1 from the official Apache distribution mirrors or Maven Central Repository
  3. Stop all services and applications that depend on the affected Helix instance
  4. Backup the existing Helix configuration, metadata store data, and any custom configurations
  5. Replace the existing helix-rest and helix-server JAR files with version 2.0.1, or update Maven/dependency management to specify version 2.0.1
  6. Verify that the CORSFilter has been updated in the new version by inspecting org.apache.helix.rest.server.filters.CORSFilter
  7. Restart the Helix services and confirm they start successfully
  8. Test the REST API endpoints with cross-origin requests to verify that the CORS policy is now restrictive (should no longer allow arbitrary origins with credentials)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Helix Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57111 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57111 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data