This advisory was last updated on 19 November 2026Version 1.0 (Final)

rConfig Security Advisory

Apache default HTTPS site could expose rConfig files on RHEL-family installs

Published

High

Advisory ID
rCFG-SA-2026-15
First Published
19 November 2026
Last Updated
19 November 2026
Version
1.0 (Final)
Status
Fixed
Affected component
Apache configuration on RHEL-family installs
CVE
Not assigned
CVSS Score
7.5 (CVSS 3.1)
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

What happened

On some RHEL-family installs, Apache's stock HTTPS site served the whole web folder instead of only rConfig's public folder. Anyone who could reach the server over HTTPS could download rConfig's .env file, which holds the database password, the application key and other secrets, and in Pro could list stored files. The rConfig Apache Security Check finds and fixes this.

Who is affected

  • rConfig Pro, Vector and Prism V8, and rConfig Core V8, installed on Rocky Linux, AlmaLinux, RHEL, CentOS Stream or Amazon Linux where Apache's stock HTTPS site was active.
  • Ubuntu and Docker installs are not affected.

Fixed in

Where the fix is available
ProductFixed in
rConfig Pro, Vector and PrismDeploy and update scripts from 19 November 2026 run the rConfig Apache Security Check automatically. Pro 8.4.3 also ships a hardened vhost template.
rConfig Core8.2.23 runs the check on install and update.
Any versionRun the check by hand (see What to do).

What to do

1. Test your server

From any machine that can reach the server, run the line for your edition. Replace SERVER with the server's IP address or hostname. Each line prints a path and its status code only. A 200 means the file is reachable. A 403, a 404, a redirect or 000 is fine.

rConfig Pro, Vector and Prism
for p in /rconfig8/current/.env /rconfig8/persistentData/.env /rconfig8/persistentData/storage/; do echo "$p $(curl -sk -o /dev/null -w '%{http_code}' https://SERVER$p)"; done
rConfig Core
for p in /rconfig/.env /rconfig/storage/logs/laravel.log; do echo "$p $(curl -sk -o /dev/null -w '%{http_code}' https://SERVER$p)"; done

2. Run the rConfig Apache Security Check

On the rConfig server, as root, run the check. It lists the fixes and asks before changing anything, and the default answer is No. Every file is backed up first. To review without changing anything, add -s -- --check after bash.

Run the check
curl -fsSL https://dl.rconfig.com/downloads/rconfig-apache-check.sh | bash

Full steps, what the check changes and how to undo it

If the files were reachable

If the test showed 200, check your Apache access logs for requests to the .env file and the storage folders. If you find requests you don't recognise, change the database password, the Redis password and any mail credentials in .env, and revoke and recreate rConfig API tokens. Do not regenerate APP_KEY on its own: rConfig uses it to encrypt stored device credentials, so contact us first.

How to check whether the files were accessed

Timeline

Timeline of events
DateEvent
18 November 2026Issue reported to rConfig.
19 November 2026Fix released: the rConfig Apache Security Check, run by Pro, Vector and Prism deploy scripts and by rConfig Core 8.2.23.
19 November 2026Advisory published.

Questions about your rConfig deployment?