How severe is GHSA-24v3-254g-jv85?

No CVSS score has been assigned to GHSA-24v3-254g-jv85 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-24v3-254g-jv85?

GHSA-24v3-254g-jv85 affects the following packages: @tutao/tutanota-utils (npm). Ecosystems affected: npm.

How do I fix GHSA-24v3-254g-jv85?

Update @tutao/tutanota-utils to 314.251111.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-24v3-254g-jv85 is resolved across your whole dependency graph.

How do I detect GHSA-24v3-254g-jv85 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @tutao/tutanota-utils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-24v3-254g-jv85 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-24v3-254g-jv85 actively exploited in the wild?

No public exploit code has been indexed for GHSA-24v3-254g-jv85 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-24v3-254g-jv85 published, and has it been updated?

GHSA-24v3-254g-jv85 was published on December 19, 2025 and was last updated on December 19, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Tuta Mail has DOM attribute and CSS injection in its Contact Viewer featureGHSA-24v3-254g-jv85

Fix: tutao/tutanota@e28345f

GHSA-24v3-254g-jv85 is a security vulnerability in @tutao/tutanota-utils. A fix is available for @tutao/tutanota-utils — see the affected versions and patch details below.

Published

Dec 19, 2025

Updated

Dec 19, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 19, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@tutao/tutanota-utilsnpm

202downloads / week

Description

Impact

Users importing contacts from untrusted sources.

Specifically crafted contact data can lead to some of DOM modifications for the link button next to the field e.g. the link address can be overriden. CSS can be manipulated to give the button arbitrary look and change it's size so that any click on the screen would lead to the specified URL. Modifying event listeners does not seem to be possible so no JS can be executed (which would also be prevented by CSP).

Technical details

The data is included as part of the mithril's hyperscript selector. It is possible to define a value like ][href=https://ddg.gg][style=position:fixed;width:150vw;height:200vh which will be included in the selector passed to Mithril and will be interpreted as part of the code.

Patches

https://github.com/tutao/tutanota/commit/e28345f5f78f628f9d5c04e785f79543f01dca8b

Workarounds

Do not open contact viewer on unpatched versions. If the contact was opened, close the app or use keyboard shortcuts to switch to another part of the app.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@tutao/tutanota-utils`	all versions	314.251111.0`npm install @tutao/tutanota-utils@314.251111.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @tutao/tutanota-utils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @tutao/tutanota-utils to 314.251111.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-24v3-254g-jv85 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Users importing contacts from untrusted sources. Specifically crafted contact data can lead to some of DOM modifications for the link button next to the field e.g. the link address can be overriden. CSS can be manipulated to give the button arbitrary look and change it's size so that any click on the screen would lead to the specified URL. Modifying event listeners does *not* seem to be possible so no JS can be executed (which would also be prevented by CSP). ## Technical details The data is included as part of the [mithril's hyperscript selector](https://mithril.js.org/hyperscrip

O3 Security · Impact-Aware SCA

Is GHSA-24v3-254g-jv85 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works