CVE-2025-68383 json
Filebeat Improper Validation of Specified Index, Position, or Offset in Input
published 10mo ago modified last mo. also EUVD-2025-204418 , GHSA-2mj3-6grc-px38 , GO-2025-4252
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
Improper Validation of Specified Index, Position, or Offset in Input (CWE-1285) in Filebeat Syslog parser and the Libbeat Dissect processor can allow a user to trigger a Buffer Overflow (CAPEC-100) and cause a denial of service (panic/crash) of the Filebeat process via either a malformed Syslog message or a malicious tokenizer pattern in the Dissect configuration.
Patch / fix
- go github.com/elastic/beats/v7 7.0.0-alpha2.0.20251204214633-dd3af18220bf, 8.19.9, 9.1.9, 9.2.3
- elastic filebeat 8.19.9, 9.1.9, 9.2.3
- elasticsearch filebeat 8.19.9, 9.1.9, 9.2.3
- elastic beats 7.0.0-alpha2.0.20251204214633-dd3af18220bf
- elasticsearch beats 7.0.0-alpha2.0.20251204214633-dd3af18220bf
- govulncheck-vulndb openSUSE Leap 15.6 0.0.20260123T022811-150000.1.140.1
suse advisories SUSE-SU-2026:0292-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
Is CVE-2025-68383 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10mo ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/elastic/beats/v7 | >=7.7.0, <8.19.9 >=9.0.0, <9.1.9 >=9.2.0, <9.2.3 <7.0.0-alpha2.0.20251204214633-dd3af18220bf >=7.7.0 |
8.19.9 9.1.9 9.2.3 7.0.0-alpha2.0.20251204214633-dd3af18220bf |
| go | github.com/elastic/beats | <=7.6.2 all versions |
no fix listed |
Affected products
- Elastic Filebeat
Classification
References
-
github.com
/elastic/beats/commit/27a168fb1c598d4a16748e9a7382bc0d197335a5
web, patch
-
github.com
/elastic/beats/commit/2f971a057eea68e057b47829950cd8c26805df30
web, patch
-
github.com
/elastic/beats/commit/339fa3f887a14c91e0c955b50a3b8819393bd632
web, patch
-
discuss.elastic.co
/t/filebeat-8-19-9-9-1-9-and-9-2-3-security-update-esa-2025-32/384180
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-68383
advisory
-
github.com
/elastic/elasticsearch
package
-
github.com
/advisories/GHSA-2mj3-6grc-px38
advisory
Sources
- CVE List CVE-2025-68383
- GitHub Advisory GHSA-2mj3-6grc-px38
- NVD CVE-2025-68383
- OSV GO-2025-4252
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.