<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T06:40:16.029165+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-250203</id>
    <title>EUVD-2026-250203</title>
    <updated>2026-10-07T06:40:16.031332+00:00</updated>
    <content>EUVD-2026-250203</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-250203"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-55740</id>
    <title>fkie_cve-2025-55740</title>
    <updated>2026-10-07T06:40:16.031368+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>nginx-defender is a high-performance, enterprise-grade Web Application Firewall (WAF) and threat detection system engineered for modern web infrastructure. This is a configuration vulnerability affecting nginx-defender deployments. Example configuration files
config.yaml and docker-compose.yml contain default credentials (default_password: "change_me_please", GF_SECURITY_ADMIN_PASSWORD=admin123). If users deploy nginx-defender without changing these defaults, attackers with network access could gain administrative control, bypassing security protections. The issue is addressed in v1.5.0 and later.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-55740"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-pr72-8fxw-xx22</id>
    <title>GHSA-pr72-8fxw-xx22 — Default Credentials in nginx-defender Configuration Files</title>
    <updated>2026-10-07T06:40:16.031404+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/Anipaleja/nginx-defender</p>
<p>### Impact
This is a configuration vulnerability affecting nginx-defender deployments. Example configuration files 
[config.yaml](https://github.com/Anipaleja/nginx-defender/blob/main/config.yaml), [docker-compose.yml](https://github.com/Anipaleja/nginx-defender/blob/main/docker-compose.yml) contain default credentials (`default_password: "change_me_please"`, `GF_SECURITY_ADMIN_PASSWORD=admin123`). If users deploy nginx-defender without changing these defaults, attackers with network access could gain administrative control, bypassing security protections.</p>
<p>**Who is impacted?**
All users who deploy nginx-defender with default credentials and expose the admin interface to untrusted networks.</p>
<p>### Patches
The issue is addressed in v1.5.0 and later.</p>
<p>Startup warnings are added if default credentials are detected.
Documentation now strongly recommends changing all default passwords before deployment.
Patched versions:
1.5.0 and later
**Will be fully patched in v1.7.0 and later**</p>
<p>### Workarounds
Users can remediate the vulnerability without upgrading by manually changing all default credentials in configuration files before deployment:
```yaml
# config.yaml
auth:
  default_password: "your_strong_password_here"
```</p>
<p>```yml
# docker-compose.yml
- GF_SECURITY_ADMIN_PASSWORD=your_strong_password
```
Restrict access to the admin interface and use environment variables for secrets.</p>
<p>### References
- [Security Configuration Guide](https://github.com/Anipaleja/nginx-defender/blob/main/d…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-pr72-8fxw-xx22"/>
  </entry>
</feed>
