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 machine-readable feed, and Security Center uses it to show which advisories apply to your server and why.

https://www.rconfig.com/security-advisories/feed.json

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 keeps up to two copies of the feed and uses the newer one, going by the generated_at date inside the file. A copy that is not a valid feed, such as a truncated download, is ignored.

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 download the feed over HTTPS daily at 03:45 (rconfig:security:refresh-advisories) and keep it in storage/app/security/advisories.json. “fetched from rconfig.com”

The daily refresh is a plain download over HTTPS with certificate checks on. It sends no data about your install. It is skipped when rConfig cannot reach rconfig.com, including when connectivity is set to offline, and the public demo site never runs it. A failed or invalid download leaves the copy in use unchanged.


On Settings > Security Center, the advisories card says where the data came from and how old it is, for example “Advisory data fetched from rconfig.com, 2 h ago” or “Advisory data bundled with this release, 12 days ago”.

The check advisories.feed_fresh records the same source and age. On an install that refreshes daily, it warns when the copy in use is more than 30 days old, because that means the refresh has stopped working. To refresh by hand on an online install:

Terminal window
cd /var/www/html/rconfig8
php artisan rconfig:security:refresh-advisories

An install that cannot reach rconfig.com uses the bundled copy, and each rConfig upgrade brings a newer one. Here advisories.feed_fresh passes and shows the bundled copy’s age for information, so an offline server is never flagged just for being offline. The same applies when the refresh is turned off. Check rconfig.com/security-advisories from a connected machine between upgrades.


To stop the daily download, set this in .env and rebuild the config cache:

Terminal window
SECURITY_ADVISORY_REFRESH=false
Terminal window
cd /var/www/html/rconfig8
php artisan config:cache

rConfig then uses the bundled copy, the same as an offline install.


The feed is plain JSON with an open CORS header, so you can read it from monitoring or compliance tooling.

{
"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" }] }
}