dbcve.org
Lucene.netApplication · Apache

CVE-2026-47896

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 through 4.8.0-beta00017. 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 · high 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 through specially crafted path inputs in the replicator component.

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
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 Lucene.Net.Replicator version
    Check the installed version of Apache Lucene.Net.Replicator.dll in your application or dependencies. This can be done via NuGet package manager, the assembly version property, or by examining your project dependencies file (packages.config, .csproj, or .deps.json).
    Affected if The installed version falls between 4.8.0-beta00005 and 4.8.0-beta00017 inclusive.
  2. Confirm replicator component is in use
    Determine whether your application actually utilizes the Lucene.Net.Replicator namespace or classes. Search your codebase for references to Lucene.Net.Replicator or examine your deployed assemblies for Lucene.Net.Replicator.dll.
    Affected if The replicator component is deployed and actively used by your application.
  3. Review replicator configuration
    Examine any configuration files or code that initialize the replicator component, looking for settings that control the restricted directory or file access paths.
    Affected if A restricted directory is configured and the replicator handles external path inputs.
  4. Audit incoming replicator requests
    If your application exposes the replicator service over a network interface, review access logs or network traces for requests containing path traversal sequences such as ../ or absolute paths.
    Affected if The replicator endpoint accepts and processes external path input without validation.

You are affected if your environment runs Apache Lucene.Net.Replicator version 4.8.0-beta00005 through 4.8.0-beta00017 and the replicator component is actively handling path inputs from external sources.

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. Identify all project dependencies using Apache Lucene.Net.Replicator version 4.8.0-beta00005 through 4.8.0-beta00017
  2. Update the NuGet package reference for Lucene.Net.Replicator to version 4.8.0-beta00018
  3. Rebuild and test the application to verify the upgrade does not introduce regressions

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

Fix this in Lucene.net Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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