dbcve.org
Alfresco Content ServicesApplication · Hyland

CVE-2026-26336

HIGH · 7.5 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 25.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
Hyland Alfresco allows unauthenticated attackers to read arbitrary files from protected directories (like WEB-INF) via the "/share/page/resource/" endpoint, thus leading to the disclosure of sensitive configuration files.

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 confidence

Hyland Alfresco contains a path traversal vulnerability in the '/share/page/resource/' endpoint that allows unauthenticated attackers to read arbitrary files from protected directories such as WEB-INF. This exposes sensitive configuration files and other confidential data without requiring authentication.

MitigationRestrict or disable the vulnerable '/share/page/resource/' endpoint, implement strict path validation to block directory traversal sequences (e.g., '../'), and ensure web server configuration denies access to sensitive directories outside the web root.

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
Alfresco Content ServicesApplication
Affected:< 25.3>= 7.4.0, <= 7.4.2.5>= 23.1, <= 23.6.0>= 25.1, <= 25.2

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

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

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

  1. Identify the installed Hyland Alfresco version
    Check the Alfresco Content Services version through the admin console, about page, or version file in the installation directory (such as version.properties or pom.xml in the WEB-INF directory)
    Affected if The installed version falls into any of these ranges: < 7.4.0; >= 7.4.0 through 7.4.2.5; >= 23.1 through 23.6.0; >= 25.1 through 25.2; or < 25.3 (meaning 25.2.x and earlier)
  2. Confirm the /share/page/resource/ endpoint is accessible
    Attempt to access the endpoint via HTTP request (e.g., GET /share/page/resource/) on the Alfresco server. This endpoint is typically enabled by default in affected installations.
    Affected if The endpoint responds without being blocked or returning a 403/404 error, indicating it is accessible to unauthenticated users
  3. Verify web server configuration allows access to WEB-INF
    Check the web server or application server configuration (such as Tomcat's server.xml or web.xml) to confirm that access to the WEB-INF directory is not explicitly denied. Also attempt a controlled test request using '../' traversal sequences to the /share/page/resource/ endpoint.
    Affected if The web server configuration does not explicitly block directory traversal or restrict access to WEB-INF, allowing the path traversal vulnerability to be exploited

You are affected if your Hyland Alfresco Content Services version is in the vulnerable ranges AND the /share/page/resource/ endpoint remains accessible and unmitigated by path validation rules.

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

Restrict or disable the vulnerable '/share/page/resource/' endpoint, implement strict path validation to block directory traversal sequences (e.g., '../'), and ensure web server configuration denies access to sensitive directories outside the web root.

Recommended fix High confidence

Upgrade to ACS 25.3+ (for 25.x), 7.4.3+ (for 7.4.x), or 23.7+ (for 23.x)

  1. Identify your current Alfresco Content Services version from the affected list (< 25.3, 7.4.0-7.4.2.5, 23.1-23.6.0, or 25.1-25.2)
  2. Backup your current Alfresco configuration and data before proceeding with any upgrade
  3. Stop the Alfresco services to prevent data inconsistency during upgrade
  4. Upgrade to Alfresco Content Services version 25.3 or later for the 25.x branch
  5. For 7.4.x branch users, upgrade to version 7.4.3 or later (the first version containing the fix)
  6. For 23.x branch users, upgrade to version 23.7 or later (the first version containing the fix)
  7. After upgrade, verify the /share/page/resource/ endpoint no longer allows unauthenticated access to protected directories like WEB-INF
  8. Restart Alfresco services and confirm normal operation
Caveat Review release notes for your specific upgrade path as minor version jumps may include configuration or API changes; test in non-production environment first

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

Fix this in Alfresco Content Services Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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