dbcve.org
Sling Resource MergerApplication · Apache

CVE-2023-26513

HIGH · 7.5 CVSS v3.1 Published 2023-03-20
Fix available
A fix is available. Upgrade to 1.4.2 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
Excessive Iteration vulnerability in Apache Software Foundation Apache Sling Resource Merger.This issue affects Apache Sling Resource Merger: from 1.2.0 before 1.4.2.

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

Apache Sling Resource Merger versions 1.2.0 through 1.4.1 contain an Excessive Iteration vulnerability that allows attackers to cause denial of service through unbounded loops, likely during resource merging operations. The CVSS 7.5 score indicates high-severity impact on availability.

MitigationUpgrade Apache Sling Resource Merger to version 1.4.2 or later, which contains the fix for the excessive iteration vulnerability.

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
Sling Resource MergerApplication
Affected:>= 1.2.0, < 1.4.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
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 Apache Sling Resource Merger version
    Locate the sling-merge JAR or bundle in your deployment (check WEB-INF/lib, osgi/bundles, or Maven dependencies). Inspect the manifest file (META-INF/MANIFEST.MF) or pom.xml for the Bundle-Version or artifact version.
    Affected if Version cannot be determined or is not listed
  2. Compare installed version to affected range
    Check if the identified version falls within >= 1.2.0 and <= 1.4.1. If using Maven, run: mvn dependency:tree | grep sling-merge or mvn dependency:list | grep sling-merge
    Affected if Version is 1.2.0, 1.3.0, 1.4.0, or 1.4.1
  3. Verify resource merger is in use
    Search your codebase for usage of org.apache.sling.resourcemerger.MergedResource or related merger APIs. Check Sling resource resolver configurations for merge enabled resources.
    Affected if Resource merger API is actively called or configured in your application
  4. Check for unbounded merge configurations
    Review your merge definitions (often in /libs or /apps resource trees) for any that could produce deeply nested or recursive resource structures without depth limits.
    Affected if Merge configurations allow deep or recursive resource trees without explicit depth limits

You are affected if Apache Sling Resource Merger version is between 1.2.0 and 1.4.1 inclusive AND your application uses resource merging operations on potentially large or nested resource trees.

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

Upgrade Apache Sling Resource Merger to version 1.4.2 or later, which contains the fix for the excessive iteration vulnerability.

Recommended fix High confidence

1.4.2

  1. Locate the dependency declaration for org.apache.sling:sling-resource-merger in your project's build configuration (pom.xml, build.gradle, or equivalent)
  2. Update the version of org.apache.sling:sling-resource-merger from your current version to version 1.4.2 or later
  3. Run your project's build and test suite to verify the upgrade does not introduce regressions
  4. Rebuild and redeploy your application
Caveat Review Apache Sling Resource Merger release notes between your current version and 1.4.2 for any API or behavioral changes that may affect your application

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

Fix this in Sling Resource Merger Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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