[FALSE-NEGATIVE] error-logs template fails to detect exposed log files without Content-Type header

[kayra-s4e]

Template IDs or paths

- http/exposures/logs/error-logs.yaml

Environment

- OS: MacOs Tahoe 26.0.1
- Nuclei: v3.4.10
- Go: go version go1.21.5 darwin/arm64

Steps To Reproduce

1. Run the error-logs template against a target that exposes a log file (e.g. /error.log).
2. The server responds with HTTP 200 and valid log content in the response body, but no Content-Type header (or a different one, such as text/html).
3. Observe that Nuclei does not generate a finding, even though the response body clearly contains log indicators (e.g. Exception, Fatal, Array, etc.).

Command used:

nuclei -u https://example.com -t http/exposures/logs/error-logs.yaml -debug

Relevant dumped responses

HTTP/1.1 200 OK
Date: Wed, 08 Oct 2025 10:19:58 GMT
Server: Apache/2.4.18 (Ubuntu)
Strict-Transport-Security: max-age=15768000; includeSubDomains; preload
Last-Modified: Thu, 08 Feb 2024 07:09:44 GMT
ETag: "1f433-610d97ef1fe00"
Accept-Ranges: bytes
Content-Length: 128051
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive

Fatal error: Uncaught Exception: Something went wrong in /var/www/html/index.php:12
Stack trace:
#0 {main}
  thrown in /var/www/html/index.php on line 12

Anything else?

No response

[Akokonunes]

Hello @kayra-s4e

Thanks for reporting this issue. The root cause is the Content-Type header matcher requiring text/plain or application/octet-stream, We'll take a look at updating the matchers to cover, PR incoming.