CVE-2026-47896: Apache Lucene.Net · Path Traversal
Affects Apache Lucene.NetSource CVE Database V5
Not known to be exploited · CVSS 8.9 High : upgrade to 4.8.0-beta00018 soon.
Data as of 14 Nov 2026, 20:44 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.8.0-beta00018
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/AU:Y/RE:LExploitation evidence
Disclosed: evidence found.
CVE published 3 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade Apache Lucene.Net and Lucene.Net.Replicator to 4.8.0-beta00018.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Lucene.Net | Affected
| Fixed in
|
NuGetLucene.Net.Replicatorpkg:nuget/Lucene.Net.ReplicatorOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade Apache Lucene.Net Replicator to version 4.8.0-beta00018, which fixes the path traversal vulnerability. Patch status is not explicitly confirmed beyond the upgrade recommendation; users should verify with the vendor advisory for the latest remediation guidance.
Description
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.