dbcve.org
Lucene.netApplication · Apache

CVE-2026-47897

HIGH · 7.5 CVSS v3.1 Published 2026-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Lucene.Net (Lucene.Net.Replicator library). This issue affects Apache Lucene.Net.Replicator: from 4.8.0-beta00005 before 4.8.0-beta00018. Users are recommended to upgrade to version 4.8.0-beta00018, 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 · moderate confidence

A path traversal vulnerability exists in Apache Lucene.Net.Replicator versions 4.8.0-beta00005 through 4.8.0-beta00017, allowing attackers to access files outside the intended restricted directory by manipulating file paths with '../' sequences. This improper limitation of pathname to a restricted directory could enable unauthorized file system access with high severity impact (CVSS 7.5).

MitigationUpgrade Apache Lucene.Net.Replicator to version 4.8.0-beta00018 or later to remediate this 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
Lucene.netApplication
Affected:= 4.8.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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 Lucene.Net.Replicator is installed
    Check your project's NuGet package references for package 'Lucene.Net.Replicator' or 'Apache-Lucene.Net.Replicator', or inspect the loaded assemblies in your application for 'Lucene.Net.Replicator' namespace
    Affected if The Replicator package or assembly is present in your environment
  2. Determine the installed version
    Check the NuGet package version or assembly version of Lucene.Net.Replicator.dll. Compare it against the vulnerable range: 4.8.0-beta00005 through 4.8.0-beta00017
    Affected if The installed version falls within 4.8.0-beta00005 to 4.8.0-beta00017 (versions 4.8.0-beta00018 and later are not affected)
  3. Verify if the Replicator service is enabled
    Inspect your application configuration, startup code, or service registration for instances of 'Replicator' or calls to 'Lucene.Net.Replicator' classes such as 'ReplicatorServer' or 'ReplicatorClient'
    Affected if The Replicator component is actively initialized or exposed as a service in your application

You are affected if Apache Lucene.Net.Replicator version 4.8.0-beta00005 through 4.8.0-beta00017 is installed AND the Replicator functionality is enabled in your environment

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache Lucene.Net.Replicator to version 4.8.0-beta00018 or later to remediate this vulnerability.

Recommended fix High confidence

4.8.0-beta00018

  1. Verify the current Lucene.Net.Replicator version in your project (check .csproj, packages.config, or NuGet package manager)
  2. Update the NuGet package reference to Lucene.Net.Replicator version 4.8.0-beta00018 using: dotnet add package Lucene.Net.Replicator --version 4.8.0-beta00018, or update via Visual Studio NuGet Package Manager
  3. Run dotnet restore to ensure dependencies are resolved
  4. Rebuild the project to verify the upgrade does not introduce compilation errors
  5. Run existing tests to confirm the path traversal fix does not break expected functionality

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

Fix this in Lucene.net Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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