Comparison Overview
The French Institute in India

The French Institute in India
2, APJ Abdul Kalam Rd, New Delhi, 110011, IN
Last Update: 12/06/2026
The French Institute / IFI (Institut français en Inde) is a section of the Embassy of France responsible for promoting and nurturing people-to-people ties between France and India. IFI performs numerous functions: from promoting academic and scientific exchanges between...

France Travail
1, avenue du docteur Gley, Paris, FR, 75020
Last Update: 03/04/2026
France Travail est un acteur majeur du marché de l’emploi en France où il s’investit pour faciliter le retour à l’emploi des demandeurs d’emploi et offrir aux entreprises des réponses adaptées à leurs besoins de recrutement. Les 55 000 collaborateurs de France Travail...
Compliance Ranges Comparison

The French Institute in India







France Travail






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
The French Institute in India has 29.58% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for France Travail in 2026.
Incident History - The French Institute in India (X = Date, Y = Severity)
The French Institute in India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - France Travail (X = Date, Y = Severity)
France Travail cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

The French Institute in India

France Travail
FAQ
Latest Global CVEs
The CONS_HISTORY ioctl handler did not adequately validate the requested history size. A large value caused an integer overflow in the buffer size calculation, resulting in a heap allocation smaller than expected. Subsequent initialization of the buffer wrote beyond the end of the allocation. An unprivileged local user with access to a vt(4) device can trigger an out-of-bounds write in the kernel, potentially escalating privileges.
The ELF image activator cleared per-process ASLR preference flags for setuid binaries after the code that computes the PIE base address, rather than before. As a result, a user-requested ASLR disable was still in effect at the point where the base address was chosen. An unprivileged local user can disable ASLR for a setuid PIE binary by calling procctl(2) before execve(2). This makes exploitation of any separate memory corruption vulnerability in that binary significantly easier.
Second, the audio buffer backing a mapping could be freed when the device was closed even though the mapping remained valid. The freed memory could then be reused elsewhere while still accessible through the stale mapping. The /dev/dsp device nodes are world-accessible by default. On a system with an audio device, either issue allows an unprivileged local user to read and write kernel memory, which can be used to escalate privileges, potentially gaining full control of the affected system. At a minimum, an attacker can crash the kernel, resulting in a Denial of Service (DoS).
The Linuxulator determined whether a binary was set-user-ID or set-group-ID by checking the P_SUGID process flag. During execve(2), this flag is not yet set at the point where the auxiliary vector is constructed, so AT_SECURE was incorrectly set to zero for set-user-ID and set-group-ID executables. An unprivileged local user can inject a shared library via LD_PRELOAD into a set-user-ID or set-group-ID Linux binary, gaining the privileges of that binary.
The kernel handler for IPV6_MSFILTER dropped a serializing lock in order to copy the source-filter list from userspace, then reacquired the lock. During this window another thread could free the multicast filter structure, leaving the handler with a stale pointer to freed memory. An unprivileged local user can exploit this use-after-free to escalate privileges.