CVE-2020-26936
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 · uneditedCloudera Data Engineering (CDE) before 1.1 was vulnerable to a CSRF attack.
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 · moderate confidenceCloudera Data Engineering (CDE) versions prior to 1.1 contained a Cross-Site Request Forgery (CSRF) vulnerability that could allow attackers to execute unauthorized actions on behalf of authenticated users. The specific attack vector and impacted endpoints are not detailed in available documentation, but CSRF attacks typically exploit the trust a web application places in authenticated browser requests.
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< 1.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify CDE version via Cloudera ManagerLog into Cloudera Manager admin interface, navigate to Cloudera Data Engineering service, and locate the version information typically displayed in the service status or about sectionAffected if The displayed version number is less than 1.1 (for example, 1.0.x or any version prior to 1.1)
-
Identify CDE version via command lineUse Cloudera Manager command line tools (cloudera manager agent) or query the CDE service API endpoint if accessible, to retrieve the installed CDE version stringAffected if The retrieved version string indicates a release prior to version 1.1
-
Check CDE component package versionsIf you have direct access to the CDE host servers, query the installed package manager (rpm, dpkg) for cloudera-data-engineering packages and their installed versionsAffected if Package version installed is lower than the version bundled in CDE 1.1 release
-
Verify CDE web interface is in useConfirm that users access CDE through its web-based console or API endpoints for job submission and managementAffected if The CDE web interface is active and the version is below 1.1, making CSRF exploitation possible
If Cloudera Data Engineering is installed and its version is anything earlier than 1.1, the environment is vulnerable to the CSRF attack described in this CVE.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1.1
Upgrade to CDE version 1.1 or later, which contains the fix for this CSRF vulnerability. If immediate upgrading is not feasible, consider implementing additional CSRF protections such as checking Origin/Referer headers or implementing custom token-based protections at the application level.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-26936 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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