Authorization Flaw in Apache (CVE-2026-66082)
Summary
Vulnerability in Apache (CVE-2026-66082). Data can be tampered with by attackers. Exploitable via POST /projects/{projectCode}/schedules/{id}/online.
Original description
The description as published by the source.
An authorization bypass vulnerability in Apache DolphinScheduler allows authenticated users to perform unauthorized operations on workflow schedules, workflow definitions, and task instances in other projects.
The affected endpoints check permissions against the supplied projectCode but fail to verify that the target resource belongs to that project. An authenticated user with the required permissions in one project can supply that project's code together with a resource identifier from another project, bypassing the target project's access restrictions.
The affected endpoints include:
POST /projects/{projectCode}/schedules/{id}/online and /offline: Activate or deactivate workflow schedules in another project.
POST /projects/{projectCode}/workflow-definition/{code}/release: Change the ONLINE/OFFLINE state of workflow definitions in another project.
Successful exploitation allows users to alter workflow availability and interfere with task execution in projects they are not authorized to access.
This issue affects Apache DolphinScheduler: before 3.4.3.
Users are recommended to upgrade to version 3.4.3, which fixes the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-66082 has been found in Apache.
Attackers can target a specific entry point like POST /projects/{projectCode}/schedules/{id}/online over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Apache CVE-2026-66082" on the vendor's site.
CVE-2026-66082 (Apache) — CWE-863 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /projects/{projectCode}/schedules/{id}/online / POST /projects/{projectCode}/workflow-definition/{code}/release
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in Apache. Attackers reach the vulnerable code path via POST /projects/{projectCode}/schedules/{id}/online.
Check the vendor advisory for the affected versions of Apache. Attack surface: POST /projects/{projectCode}/schedules/{id}/online / POST /projects/{projectCode}/workflow-definition/{code}/release.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /projects/{projectCode}/schedules/{id}/online requests with malformed payloads or SQL meta-characters. Run grep -r 'Apache' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Apache' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Apacheを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /projects/{projectCode}/schedules/{id}/online' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /projects/{projectCode}/schedules/{id}/onlineへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /projects/{projectCode}/schedules/{id}/online on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web security@apache.org
- web openwall.com
- web github.com