Recently active topics

Dear Customers and users, On October 20, 2026, the PHP Security Team announced the upcoming release of fixes for two critical vulnerabilities in PHP, both rated CVSS 9.2 and publicly referenced as CVE-2026-109618 and CVE-2026-109619.As Centreon Infra Monitoring relies on PHP, our Security and R&D teams have initiated an immediate assessment to determine:which Centreon versions and supported environments may be affected; whether the vulnerabilities are exploitable through a standard Centreon deployment; which security updates or mitigating measures may be required.At the time of this notice, the PHP Security Team has not yet published the complete technical details, confirmed affected versions or fixed releases. We therefore cannot yet confirm that Centreon installations are exploitable.We are not currently aware of any exploitation specifically targeting Centreon products through these vulnerabilities.As a general security reminder, Centreon platforms must be kept fully up to date.

Please note that the only procedures supported and maintained by Centreon are those published in the official documentation. If you have a question about this article, post it in the comments.Use this procedure if you are running Centreon 24.04, 24.10 or 25.10 on Debian 12 and you wish to upgrade to Centreon 26.10 (only Debian 13 is supported for this version).Run every command as root. Read each comment in the code blocks before running commands. Step 1: Before you start1.1 Take a snapshot of each serverSnapshot every server (central server, database server, MAP server, MBI server). If you have a remote database, take both snapshots at the same time, with Centreon stopped if possible. It is the only way to roll back quickly.1.2 Create dumpsSnapshots let you roll back a whole server quickly, but they do not replace backups. They usually share the VM's storage, capture databases only in a crash-consistent state, and cannot restore a single database or file. Once your snapshots are done,

I am encountering persistent authentication issues while trying to access the REST API of a Dell ME4012 storage system. Despite providing valid credentials and testing multiple configurations, the REST API consistently returns an Authentication Unsuccessful error.Steps to ReproduceAttempt to log in to the Dell ME4012 REST API using curl:curl -k -X POST https://192.168.1.3/api/login \ -H "Content-Type: application/json" \ -d '{"username": "Admin", "password": "Password"}'Observe the following response:<RESPONSE VERSION="L100"> <OBJECT basetype="status" name="status" oid="1"> <PROPERTY name="response" type="string" display-name="Response">Invalid sessionkey</PROPERTY> </OBJECT></RESPONSE>Attempted the same with both controllers (192.168.1.3 and 192.168.1.4), but the same error occurs.Repeated the test with:HTTP Basic AuthenticationBoth curl and the centreon_dell_me4_restapi.pl pluginNo changes in the outcome.Expected BehaviorAuthentication shoul

A new update for Centreon pp manager 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-pp-manager-26.10.0

A new update for Centreon mbi 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-mbi-26.10.0

A new update for Centreon map 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-26.10.0

A new update for Centreon license manager 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-license-manager-26.10.0

A new update for Centreon it edition extensions 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-it-edition-extensions-26.10.0

A new update for Centreon bam 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-bam-26.10.0

A new update for Centreon autodiscovery 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-autodiscovery-26.10.0

A new update for Centreon anomaly detection 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-anomaly-detection-26.10.0

A new update for Centreon web 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-26.10.0

A new update for Centreon open tickets 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-open-tickets-26.10.0

A new update for Centreon ha 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-ha-26.10.0

A new update for Centreon dsm 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-dsm-26.10.0

A new update for Centreon awie 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-awie-26.10.0

A new update for Centreon common 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-common-26.10.0

A new update for Centreon gorgone 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-gorgone-26.10.0

A new update for Centreon monitoring agent 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-monitoring-agent-26.10.0

A new update for Centreon collect 26.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-collect-26.10.0

The new RUST plugins (will) supports SNMPv1?I’m testing on a device that allow only v1 and it seems no.snmpwalksnmpwalk -v1 -c **** 10.*.*.* .1.3.6.1.2.1.1.1SNMPv2-MIB::sysDescr.0 = STRING: ****with rs plugin/usr/lib/centreon/plugins/centreon-plugin-rust-snmp -H 10.*.*.* -v 1 -c **** --json /usr/lib/centreon/plugins/rs-collections/applications-protocol-snmp/sysdesc.json --check-responseUNKNOWN: Could not connect to 10.*.*.*:161 is the hostname and the snmp community correct ? Resource temporarily unavailable (os error 11)With TCPdump I see that it force SNMPv2c GetBulk, a function not present on SNMPv111:41:08.191089 IP (tos 0x0, ttl 64, id 14733, offset 0, flags [DF], proto UDP (17), length 68) 10.*.*.*.59760 > 10.*.*.*.161: [bad udp cksum 0x3caa -> 0x6f89!] { SNMPv2c C="*" { GetBulk(24) R=1 N=1 M=1 .1.3.6.1.2.1.1.1 } }