dbcve.org
JenaApplication · Apache

CVE-2025-49656

HIGH · 7.5 CVSS v3.1 Published 2025-07-21
Fix available
A fix is available. Upgrade to 5.5.0 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
Users with administrator access can create databases files outside the files area of the Fuseki server. This issue affects Apache Jena version up to 5.4.0. Users are recommended to upgrade to version 5.5.0, which fixes the issue.

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 Jena Fuseki server versions up to 5.4.0 contain a path traversal vulnerability allowing administrators to create database files outside the designated files area, potentially enabling arbitrary file write on the server.

MitigationUpgrade Apache Jena to version 5.5.0 or later to receive the patch for this directory traversal 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
JenaApplication
Affected:< 5.5.0

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 if Apache Jena Fuseki is installed
    Check for the Fuseki server by looking for the 'fuseki' executable or JAR file in common installation directories, or run 'java -jar fuseki-server.jar --version' if a JAR is present
    Affected if Apache Jena Fuseki server is found on the system
  2. Determine the installed Apache Jena version
    Run 'fuseki-server --version' or check the version displayed on the Fuseki web administration interface login page, or examine the JAR file name which typically includes the version number
    Affected if The version is 5.4.0 or lower (any version below 5.5.0)
  3. Verify the Fuseki web admin interface is accessible
    Check if the Fuseki web server is running by attempting to access the admin endpoint (typically port 3030) - check running processes for java processes running fuseki-server or check netstat for listeners on the Fuseki port
    Affected if The Fuseki admin interface is exposed and reachable on the network
  4. Check the files area configuration
    Log into the Fuseki admin interface and navigate to the dataset configuration to examine the 'Files Area' or 'Dataset Path' setting - this is the directory where database files are permitted to be created
    Affected if The files area is not explicitly set to a secure, non-system directory or uses default unrestricted settings

A user is affected if Apache Jena Fuseki version 5.4.0 or lower is running with its web admin interface accessible and the files area configuration allows writing outside the intended directory.

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

Upgrade Apache Jena to version 5.5.0 or later to receive the patch for this directory traversal vulnerability.

Recommended fix High confidence

5.5.0

  1. 1. Stop the running Apache Jena Fuseki server instance
  2. 2. Back up all existing Fuseki data, configuration files, and databases
  3. 3. Download Apache Jena version 5.5.0 from the official Apache download repository (https://jena.apache.org/download/)
  4. 4. Extract the new Jena 5.5.0 distribution package
  5. 5. Migrate the backed-up configuration files to the new installation
  6. 6. Start the Fuseki server with the new version 5.5.0
  7. 7. Verify the server starts successfully and the path traversal vulnerability is no longer present by attempting to create a test database outside the designated files area (the operation should be denied)

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

Fix this in Jena Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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