CVE-2022-26368
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 · uneditedBrowse restriction bypass and operation restriction bypass vulnerability in Cabinet of Cybozu Garoon 4.0.0 to 5.5.1 allows a remote authenticated attacker to alter and/or obtain the data of Cabinet.
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 confidenceThis is an authorization bypass vulnerability in Cybozu Garoon's Cabinet (file management) component. A remote authenticated attacker can bypass both browse restrictions (viewing unauthorized files) and operation restrictions (performing unauthorized actions) on Cabinet data, enabling unauthorized access to and/or modification of files they should not have permission to access.
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>= 4.0.0, <= 5.5.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cybozu Garoon installationIdentify whether Cybozu Garoon is deployed in your environment. This is typically a Japanese enterprise groupware/collaboration platform.Affected if Cybozu Garoon is installed and accessible to users
-
Determine installed Garoon versionAccess the Garoon system administration panel or check system files to identify the exact version number installed. Compare the version against the affected range: 4.0.0 through 5.5.1 inclusive.Affected if Installed version is 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.5.0, 4.5.1, 4.5.2, 4.5.3, 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.5.0, or 5.5.1
-
Verify Cabinet module is in useConfirm that the Cabinet (file management) component is enabled and accessible to users in your Garoon deployment. This is the specific component where the authorization bypass occurs.Affected if Cabinet module is enabled and users have access to it
-
Review Cabinet access logs for anomaliesExamine Garoon Cabinet access logs for any unauthorized file access or operations performed by users who should not have permissions to those files or actions.Affected if Logs show users accessing or modifying files outside their assigned permissions
You are affected if Cybozu Garoon version 4.0.0 through 5.5.1 is installed and the Cabinet module is enabled and accessible to users.
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 dataUpgrade Cybozu Garoon to version 5.5.2 or later to obtain the patch for this vulnerability. If immediate patching is not possible, review user access controls and monitor Cabinet activity for unauthorized access patterns.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26368 — 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-2022-26368 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