Is there an existing issue for this?
Current Behavior
Hey,
Currently, when running nuclei templates which execute javascript, Nuclei ignores the proxy flag (and others, like custom-header).
For example, running the templates:
javascript/cves/2024/CVE-2024-23897.yaml
javascript/cves/2025/CVE-2025-12101.yaml (Has both javascript and HTTP)
You can run it through BurpSuite proxy for example, and see that the request does not go through it. Same for custom-header flag, it just ignores it.
Expected Behavior
The expected behavior is that the request will go through the proxy that was set via the flag, and take into consideration flags like custom headers.
Steps To Reproduce
Run nuclei -t javascript/cves/2024/CVE-2024-23897.yaml -u TARGET --proxy PROXY -H 'Custom: Header'
Relevant log output
Environment
- OS: Ubuntu 24.04
- Nuclei: v3.5.1
- Go: 1.22.2
Anything else?
No response
Is there an existing issue for this?
Current Behavior
Hey,
Currently, when running nuclei templates which execute javascript, Nuclei ignores the proxy flag (and others, like custom-header).
For example, running the templates:
javascript/cves/2024/CVE-2024-23897.yaml
javascript/cves/2025/CVE-2025-12101.yaml (Has both javascript and HTTP)
You can run it through BurpSuite proxy for example, and see that the request does not go through it. Same for custom-header flag, it just ignores it.
Expected Behavior
The expected behavior is that the request will go through the proxy that was set via the flag, and take into consideration flags like custom headers.
Steps To Reproduce
Run nuclei -t javascript/cves/2024/CVE-2024-23897.yaml -u TARGET --proxy PROXY -H 'Custom: Header'
Relevant log output
Environment
Anything else?
No response