Unauthenticated file disclosure via CSS path traversal
Published Jan 30, 2026 · Updated Jan 30, 2026
Path traversal in OpenCTI 3.3.1 allows remote attackers to read arbitrary server files through crafted static/css requests. The static/css route resolves traversal sequences in the requested path without confining the result to its asset directory. No authentication or user interaction is required; the demonstrated consequence is file disclosure, not modification or service interruption.
Summary
What happened
Path traversal in OpenCTI 3.3.1 allows remote attackers to read arbitrary server files through crafted static/css requests. The static/css route resolves traversal sequences in the requested path without confining the result to its asset directory. No authentication or user interaction is required; the demonstrated consequence is file disclosure, not modification or service interruption.
The record
- CVE
- CVE-2020-37041
- Published
- Jan 30, 2026
- Updated
- Jan 30, 2026
- Vendor
- Filigran
- Product
- OpenCTI
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 30, 2026CVE publishedPublication date reported by the CVE source.
- Jan 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.3.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- OpenCTI 3.3.1 - Directory Traversalproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo