dbcve.org
GaroonApplication · Cybozu

CVE-2026-22888

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

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
Improper input verification issue exists in Cybozu Garoon 5.0.0 to 6.0.3, which may lead to unauthorized alteration of portal settings, potentially blocking access to the product.

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 confidence

Improper input verification in Cybozu Garoon versions 5.0.0 through 6.0.3 allows authenticated users to modify portal settings through unsanitized input, potentially rendering the portal inaccessible by altering critical configuration parameters.

MitigationApply the vendor-supplied patch or upgrade to a patched version of Cybozu Garoon; review and restore portal settings if access has been blocked.

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
GaroonApplication
Affected:>= 5.0.0, < 6.0.3

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Identify Cybozu Garoon installation
    Locate the Cybozu Garoon installation directory or access the system administrator interface. Look for version information in the admin panel or in installation files such as VERSION.txt, version.info, or similar files in the installation root directory.
    Affected if Unable to locate or confirm Cybozu Garoon installation
  2. Determine installed Garoon version
    Check the installed version through the admin console (System Settings > System Information) or by examining version files in the installation directory. Compare the version number against the affected range.
    Affected if Installed version is 5.0.0 through 6.0.3 (excluding 6.0.3)
  3. Verify portal accessibility
    Attempt to access the portal homepage or portal settings panel as an authenticated administrator. Check if the portal renders correctly and if portal configuration options are available.
    Affected if Portal is inaccessible, fails to load, or displays errors indicating corrupted configuration
  4. Review portal configuration integrity
    Access the portal settings through the administrative interface (Portal > Portal Settings) and verify that critical configuration parameters such as portal name, layout settings, and portlet configurations contain expected values and are not corrupted or blank.
    Affected if Portal settings are modified, missing, or contain unexpected values that were not set by administrators

A user is affected if Cybozu Garoon version 5.0.0 through 6.0.3 is installed AND the portal is either inaccessible or shows modified configuration parameters that were not intentionally changed.

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 6.0.3 or later
Fixed in 6.0.3
Interim mitigation

Apply the vendor-supplied patch or upgrade to a patched version of Cybozu Garoon; review and restore portal settings if access has been blocked.

Recommended fix High confidence

Garoon 6.0.3

  1. Back up the Garoon database and configuration files before proceeding with the upgrade
  2. Review the official Cybozu Garoon upgrade documentation for your current version
  3. Download Garoon version 6.0.3 or later from the official Cybozu download page
  4. Execute the upgrade installer following the standard Garoon upgrade procedure
  5. After upgrade, verify that portal settings are accessible and the product is functioning normally
  6. Confirm the Garoon version shows 6.0.3 or later in the system information
Caveat Review Garoon 6.0 release notes for any functional changes from version 5.x that may affect your workflows

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

Fix this in Garoon Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22888 — 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-22888 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