CVE-2026-35178
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 · uneditedWorkbench is a suite of tools for administrators and developers to interact with Salesforce.com organizations via the Force.com APIs. Prior to 65.0.0, Workbench contains remote code execution vulnerability in the timezone conversion flow, which processes attacker-controlled cookie values in an unsafe manner. This vulnerability is fixed in 65.0.0.
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 confidenceWorkbench versions prior to 65.0.0 contain a pre-authentication remote code execution vulnerability in the timezone conversion functionality. The application processes attacker-controlled cookie values without proper sanitization, allowing injection of malicious code that gets executed on the server.
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< 65.0.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Check installed Forceworkbench versionLocate the Workbench version from the application interface (typically displayed in the footer or about page) or check version metadata files in the installation directoryAffected if Version is lower than 65.0.0 (e.g., 64.x, 63.x, etc.)
-
Verify timezone conversion feature is accessibleNavigate to the timezone conversion tool within Workbench (usually under Utilities or Developer tools section)Affected if The timezone conversion feature is available and can be accessed by users
-
Confirm cookie-based timezone handling is in useInspect HTTP requests/responses when using the timezone conversion feature to verify that timezone preferences are stored and processed via cookiesAffected if The application stores timezone settings in cookies and processes these values server-side during conversion operations
-
Check for unsafe cookie value processingReview application logs or network traffic for any evidence of cookie values being directly concatenated into server-side operations without sanitization in the timezone flowAffected if Cookie values from the timezone feature are processed without proper input validation or encoding
You are affected if Forceworkbench version is below 65.0.0 AND the timezone conversion feature is accessible, as the vulnerability exploits unsafe cookie handling in that specific flow.
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.
dbcve · scoped65.0.0
Upgrade Workbench to version 65.0.0 or later. Prior to upgrading, consider restricting network access to the Workbench instance as a temporary compensating control.
65.0.0
- Upgrade Forceworkbench to version 65.0.0 or later
- After upgrading, verify the version in the Workbench UI (typically in the footer or About section) to confirm the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.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 $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35178 — 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-2026-35178 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