Skip to content

Security advisory feed

Every confirmed vulnerability in rConfig, or in software rConfig depends on such as PHP, gets an advisory at rconfig.com/security-advisories. From V8.5.0 the same advisories are published as a signed, machine-readable feed, and Security Review uses it to show which advisories apply to your server and why.

https://www.rconfig.com/security-advisories/feed.json the feed
https://www.rconfig.com/security-advisories/feed.json.sig its ed25519 signature

Each advisory lists the rConfig Pro, rConfig Core or PHP versions it affects, the version that fixes it, and the security check IDs that verify the fix on a running install. The feed also lists rConfig releases (marking security releases) and the end-of-support dates rConfig uses for PHP, MariaDB, MySQL, PostgreSQL and the operating system.


rConfig uses the newest feed whose signature verifies against the rConfig key built into the release. A feed that fails the check is ignored, whatever its date.

Source When Shown as
Bundled Every release ships the feed current at release time, in resources/security/advisories.json. “bundled with this release”
Live Online installs fetch the feed daily at 03:45 (rconfig:security:refresh-advisories). “fetched from rconfig.com”
Imported Offline installs import a downloaded copy. “imported”

The live refresh sends no data about your install: it is a plain download. Turn it off with SECURITY_ADVISORY_REFRESH=false. The public demo site never fetches it.


On a machine with internet access, download both files:

Terminal window
curl -fsSLO https://www.rconfig.com/security-advisories/feed.json
curl -fsSLO https://www.rconfig.com/security-advisories/feed.json.sig

Copy both to the rConfig server, then import them:

Terminal window
cd /var/www/html/rconfig8
php artisan rconfig:security:import-advisories /path/to/feed.json

The import refuses a feed whose signature does not verify. advisories.feed_fresh warns when the feed in use is more than 30 days old, so repeat the import after each new advisory, or monthly.


The feed is plain JSON with an open CORS header, so you can read it from monitoring or compliance tooling. Verify feed.json.sig (base64 ed25519 over the exact bytes of feed.json) with the public key w0uyOWsjXpeUe9sqCBONir7k1VzKFWJs2r2y3T5SWfQ= before trusting it.

{
"schema": 1,
"generated_at": "2026-11-19T17:02:33Z",
"advisories": [
{
"id": "rCFG-SA-2026-15",
"severity": "High",
"affects": [{ "product": "pro", "component": "rconfig", "range": ">=8.0.0 <8.4.3" }],
"fixed_in": { "pro": "8.4.3" },
"check_ids": ["web.env_exposed", "web.storage_exposed", "os.default_ssl_site"]
}
],
"releases": [{ "product": "pro", "version": "8.4.1", "security": true }],
"lifecycle": { "php": [{ "cycle": "8.4", "eol": "2028-12-31" }] }
}