https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T02:06:39.563656+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2022-01070 bdu:2022-01070 2026-10-06T02:06:39.567937+00:00 bdu:2022-01070 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0901 certfr-2026-avi-0901 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan… 2026-10-06T02:06:39.567971+00:00 certfr-2026-avi-0901 https://cve.radiocsirt.org/vuln/euvd-2026-234495 EUVD-2026-234495 2026-10-06T02:06:39.567989+00:00 EUVD-2026-234495 https://cve.radiocsirt.org/vuln/fkie_cve-2022-21704 fkie_cve-2022-21704 2026-10-06T02:06:39.568001+00:00

log4js-node is a port of log4js to node.js. In affected versions default file permissions for log files created by the file, fileSync and dateFile appenders are world-readable (in unix). This could cause problems if log files contain sensitive information. This would affect any users that have not supplied their own permissions for the files via the mode parameter in the config. Users are advised to update.

 https://cve.radiocsirt.org/vuln/ghsa-82v2-mx6x-wq7q GHSA-82v2-mx6x-wq7q — Incorrect Default Permissions in log4js 2026-10-06T02:06:39.568028+00:00

Affected: npm: log4js

### Impact Default file permissions for log files created by the file, fileSync and dateFile appenders are world-readable (in unix). This could cause problems if log files contain sensitive information. This would affect any users that have not supplied their own permissions for the files via the mode parameter in the config.

### Patches Fixed by: * https://github.com/log4js-node/log4js-node/pull/1141 * https://github.com/log4js-node/streamroller/pull/87

Released to NPM in log4js@6.4.0

### Workarounds Every version of log4js published allows passing the mode parameter to the configuration of file appenders, see the documentation for details.

### References

Thanks to [ranjit-git](https://www.huntr.dev/users/ranjit-git) for raising the issue, and to @lamweili for fixing the problem.

### For more information If you have any questions or comments about this advisory: * Open an issue in [logj4s-node](https://github.com/log4js-node/log4js-node) * Ask a question in the [slack channel](https://join.slack.com/t/log4js-node/shared_invite/enQtODkzMDQ3MzExMDczLWUzZmY0MmI0YWI1ZjFhODY0YjI0YmU1N2U5ZTRkOTYyYzg3MjY5NWI4M2FjZThjYjdiOGM0NjU2NzBmYTJjOGI) * Email us at [gareth.nomiddlename@gmail.com](mailto:gareth.nomiddlename@gmail.com)

 https://cve.radiocsirt.org/vuln/gsd-2022-21704 gsd-2022-21704 2026-10-06T02:06:39.568063+00:00 gsd-2022-21704 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-21704 UBUNTU-CVE-2022-21704 2026-10-06T02:06:39.568075+00:00

Affected: Ubuntu:16.04:LTS: node-log4js, Ubuntu:18.04:LTS: node-log4js, Ubuntu:20.04:LTS: node-log4js

log4js-node is a port of log4js to node.js. In affected versions default file permissions for log files created by the file, fileSync and dateFile appenders are world-readable (in unix). This could cause problems if log files contain sensitive information. This would affect any users that have not supplied their own permissions for the files via the mode parameter in the config. Users are advised to update.