VulnerabilityPublished 28 Jan 2026

CVE-2026-1466: Jirafeau · Cross-site Scripting

Affects JirafeauSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium : upgrade to 4.7.1 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.7.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Jirafeau to 4.7.1.

Affected software

Product	Affected	Fixed in
Jirafeau projectJirafeau	Affected <4.7.1	Fixed in 4.7.1
GitHubjirafeau/jirafeau`pkg:github/jirafeau/jirafeau`Other threats	Affected =0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately verify that their Jirafeau deployments send the HTTP header 'X-Content-Type-Options: nosniff' to prevent browsers from MIME sniffing and executing malicious scripts. Administrators should audit and enforce strict MIME type validation on uploaded files, rejecting or sanitizing files with ambiguous or invalid MIME types. Implementing Content Security Policy (CSP) headers can further reduce the risk by restricting script execution contexts. User education to avoid previewing suspicious files can reduce exploitation likelihood. Monitoring web server logs for unusual MIME types or preview requests can help detect attempted exploitation. If possible, upgrade to a Jirafeau version that addresses this vulnerability once available. Network-level controls such as web application firewalls (WAFs) can be configured to detect and block malformed MIME type requests. Finally, organizations should review their file sharing policies to limit exposure and ensure secure handling of file previews.

Description

CVE-2026-1466 is a medium severity cross-site scripting (XSS) vulnerability in the Jirafeau file sharing project. It arises from improper MIME type validation during browser preview of files, allowing attackers to bypass restrictions by sending manipulated HTTP requests with invalid MIME types. This causes browsers to MIME-sniff and potentially execute malicious JavaScript embedded in SVG or HTML files. The vulnerability does not require authentication but needs user interaction to trigger the preview. Although no known exploits are reported in the wild, the vulnerability can lead to limited confidentiality and integrity impacts due to script execution in the victim's browser. The issue can be mitigated by disabling MIME sniffing via the X-Content-Type-Options: nosniff header. European organizations using Jirafeau for file sharing should apply strict content-type validation and ensure security headers are properly configured to prevent exploitation.

Impact

For European organizations, this vulnerability poses a risk primarily to confidentiality and integrity of user sessions and data accessed via Jirafeau instances. Attackers could execute malicious scripts in users' browsers, potentially stealing session tokens, cookies, or performing actions on behalf of the user. This could lead to unauthorized data access or manipulation within the file sharing environment. Since Jirafeau is used for sharing files, exploitation could also facilitate the delivery of further malware or phishing attempts. The impact is heightened in sectors where sensitive or regulated data is shared, such as finance, healthcare, or government agencies. The requirement for user interaction (previewing a file) limits the scope but does not eliminate risk, especially in environments with frequent file sharing. Additionally, the cross-site scripting could be leveraged in targeted attacks against European organizations using Jirafeau, especially if combined with social engineering. The lack of known exploits suggests a window for mitigation before widespread abuse occurs.

Summary

CVE-2026-1466 is a cross-site scripting vulnerability identified in the Jirafeau project, a web-based file sharing application. The vulnerability stems from the application's mechanism to prevent browser preview of potentially dangerous file types such as SVG and HTML, which can contain executable JavaScript. Jirafeau attempts to restrict previews to files with MIME types starting with image (excluding image/svg+xml), video, or audio. However, an attacker can craft an HTTP request with an invalid MIME type, for example, 'image.', which bypasses the MIME type check. When the browser attempts to preview the file, it performs MIME sniffing to detect the actual content type, potentially recognizing it as SVG or HTML and executing embedded JavaScript code. This leads to an XSS attack vector where malicious scripts run in the context of the victim's browser session. To mitigate this, the application should disable MIME sniffing by sending the HTTP header 'X-Content-Type-Options: nosniff', instructing browsers not to override the declared content type. The vulnerability has a CVSS 3.1 score of 6.1 (medium severity), with an attack vector of network, low attack complexity, no privileges required, but requiring user interaction to trigger. The impact affects confidentiality and integrity but not availability. There are no known exploits in the wild, and no patches are currently linked, indicating the need for proactive mitigation by administrators.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Feb 2026, 09:17 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats