CERT-FR alertCERT-FR
[Màj] Multiples vulnérabilités dans PHP
CERTFR-2026-ALE-014
CERT-FR has published an alert. Check the bulletin for affected systems, recommended actions and current status.
Published Read the official source ↗
ENGINEERING · WEB & API SECURITY
Cybersecurity,
closer to
your systems.
Websites, business applications and APIs: an engineering approach to examining risk, planning remediation and preparing continuity.
Scope, resources and deliverables agreed before any engagement.
ONE SYSTEM. BOUNDARIES TO UNDERSTAND.
01IDENTITIESWho can act?
02APPLICATIONWhich rules apply?
03DATAWhich access?
04CONTINUITYHow to recover?
SCOPE → CHECKS → HANDOVERApproach diagram
WEBSITES & APPLICATIONSAPI & INTEGRATIONSREMEDIATION & CONTINUITY
WATCH / OFFICIAL SOURCES
Cybersecurity watch & alerts
Alerts, vulnerabilities and analysis: official publications to help you decide what to examine and where to verify.
Sources retrieved · 4 / 4 · Last collection : 30/10/2026 22:59 UTC
VulnerabilityCISA
Ivanti Connect Secure Generation of Predictable Numbers or Identifiers Vulnerability
CVE-2026-118527
This reference appears in the CISA catalogue of vulnerabilities with observed exploitation. Consult the measures recommended by the source and vendor.
Ivanti · Connect Secure
Exploitation observed · CISA
Added to catalogue Read the official source ↗
Cybersecurity informationCERT-FR
Bulletin d'actualité CERTFR-2026-ACT-045
CERTFR-2026-ACT-045
A CERT-FR bulletin provides analysis and recommendations to understand threats and organise prevention.
Published Read the official source ↗
01 / AREAS OF EXPERTISE
Technical risks.
Your business at stake.
Excessive access, a bypassed business rule, an uncertain recovery: start with your system and what needs to work.
01Subject to scoping02Subject to technical scoping03Commitments agreed per engagement04Research & design
Web & API security
Access, data flows and sensitive operations, considered in their business context.
Hardening & remediation
Address a risk while preserving the workflows that need to keep working.
Maintenance & continuity
Connect software versions, backups and recovery arrangements to your operations.
AI & automation
Understand the data processed, the permissions granted and the actions a system can take.
02 / OUR APPROACH
From agreed scope
to observed results.
Each step produces a useful record. Assumptions, checks and limitations remain visible.
- 01
Scope
Identify assets, workflows and authorisations.
- 02
Examine
Link each finding to an observation and its context.
- 03
Prioritise
Separate risks, dependencies and decisions.
- 04
Remediate
Prepare changes and a recovery path.
- 05
Verify
Recheck the addressed risk and preserved workflows.
- 06
Hand over
Provide results, limitations and agreed next steps.
03 / DOCUMENTATION
A deliverable should
help you decide.
Scope, finding, priority, next step: information that makes an engagement understandable and transferable.
View the deliverable templates ↗HAIDRA.DEVDeliverable template
Finding record
& action plan
- 01 · Scope
- Authorised assets and workflows
- 02 · Observation
- Expected, observed, limitations
- 03 · Decision
- Priority, owner, verification
Document structure, without client data.
04 / TECHNICAL NOTES
Understand.
Then decide.
Written by HAIDRA.DEV · 30 October 2026
A fix must also preserve what works.
Blocking a risky operation is not enough to accept a fix. The authorised user must still be able to complete their work.
Read the note
Written by HAIDRA.DEV · 30 October 2026
Back up. Restore. Recover.
A backup file does not prove that operations can resume. Recovery must be checked in a separate environment.
Read the noteTHE STARTING POINT
Let’s discuss your system.
A context, a question, a need to clarify. Start with the scope.