shaarli - Debian Package Tracker

general

source: shaarli (main)
version: 0.16.1+dfsg-1
maintainer: Debian PHP PEAR Maintainers (archive) (DMD)
uploaders: James Valleroy [DMD]
arch: all
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

oldstable: 0.12.1+dfsg-8+deb12u2
old-sec: 0.12.1+dfsg-8+deb12u2
stable: 0.14.0+dfsg-2+deb13u1
stable-sec: 0.14.0+dfsg-2+deb13u1
unstable: 0.16.1+dfsg-1

versioned links

0.12.1+dfsg-8+deb12u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
0.14.0+dfsg-2+deb13u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
0.16.1+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

shaarli (1 bugs: 0, 1, 0, 0)

action needed

Debci reports failed tests high

unstable: fail (log)
The tests ran in 0:00:57
Last run: 2026-06-23T10:29:52.000Z
Previous status: unknown

testing: pass (log)
The tests ran in 0:02:10
Last run: 2026-04-15T19:20:48.000Z
Previous status: unknown

stable: pass (log)
The tests ran in 0:01:27
Last run: 2025-11-09T13:11:07.000Z
Previous status: unknown

Created: 2026-02-24 Last update: 2026-06-27 17:31

1 binary package has unsatisfiable dependencies high

The dependencies of shaarli=0.16.1+dfsg-1 cannot be satisfied in unstable on amd64 because: unsatisfied dependency on php-parsedown-extra (< 0.9~~)

Created: 2026-06-19 Last update: 2026-06-27 17:30

A new upstream version is available: 0.16.3 high

A new upstream version 0.16.3 is available, you should consider packaging it.

Created: 2026-05-27 Last update: 2026-06-27 15:02

4 security issues in trixie high

There are 4 open security issues in trixie.

4 important issues:

CVE-2026-48821: Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a DOM-based Cross-Site Scripting (XSS) vulnerability in the Thumbnail Synchronizer feature. When an administrator runs the thumbnail update process, malicious bookmark titles are returned via an AJAX response and inserted into the DOM using innerHTML without proper sanitization. The issue originates from the interaction between the backend thumbnail update endpoint and the frontend JavaScript responsible for rendering update progress. On the backend, the ThumbnailsController::ajaxUpdate method returns bookmark data formatted using the 'raw' formatter. This includes the unescaped bookmark title in the JSON response. On the client side, the script thumbnails-update.js processes this AJAX response and dynamically updates the progress interface. Administrators using the thumbnail synchronization feature are affected and exploitation could lead to session hijacking, privilege escalation, backdoor injection and full compromise. This issue has been fixed in version 0.16.2.
CVE-2026-48822: Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a stored Cross-Site Scripting (XSS) vulnerability in the Markdown-to-HTML conversion process used in the Bookmark Description field. An authenticated user can inject a malicious javascript: URI inside a Markdown link. The vulnerability originates in the filterProtocols method within BookmarkMarkdownFormatter.php.This method attempts to sanitize Markdown links by filtering dangerous protocols (such as javascript:) before rendering. It uses the following regular expression: (#]\((.*?)\)#is). This regex is designed to detect inline Markdown links, but it fails to detect Markdown reference-style links because reference-style links are resolved by the Markdown parser after preprocessing. The filterProtocols method never inspects the actual URL used in these references and as a result, an attacker can supply a javascript: URI inside a reference definition. This issue has been fixed in version 0.16.2.
CVE-2026-48823: Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a stored Cross-Site Scripting (XSS) vulnerability in the tag filtering functionality of Shaarli. An authenticated user can inject arbitrary JavaScript into the tags field when creating a bookmark (Shaare). The malicious payload is stored and later executed when users interact with the "Filter by tag" search feature on the homepage. User-supplied input in the tags field is not properly sanitized or output-escaped before being rendered in the tag filtering interface. When a bookmark is created with a malicious payload inside the tag field, the payload is stored in the database. Later, when a user searches using the "Filter by tag" functionality on the homepage, the application renders matching tags dynamically. If the tag value contains HTML with JavaScript event handlers, it is injected into the DOM. This impacts anyone interacting with the "Filter by tag" search functionality, administrators and privileged users. This issue has been fixed in version 0.16.2.
CVE-2026-50190:

Created: 2026-06-18 Last update: 2026-06-18 20:30

4 security issues in sid high

There are 4 open security issues in sid.

4 important issues:

CVE-2026-48821: Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a DOM-based Cross-Site Scripting (XSS) vulnerability in the Thumbnail Synchronizer feature. When an administrator runs the thumbnail update process, malicious bookmark titles are returned via an AJAX response and inserted into the DOM using innerHTML without proper sanitization. The issue originates from the interaction between the backend thumbnail update endpoint and the frontend JavaScript responsible for rendering update progress. On the backend, the ThumbnailsController::ajaxUpdate method returns bookmark data formatted using the 'raw' formatter. This includes the unescaped bookmark title in the JSON response. On the client side, the script thumbnails-update.js processes this AJAX response and dynamically updates the progress interface. Administrators using the thumbnail synchronization feature are affected and exploitation could lead to session hijacking, privilege escalation, backdoor injection and full compromise. This issue has been fixed in version 0.16.2.
CVE-2026-48822: Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a stored Cross-Site Scripting (XSS) vulnerability in the Markdown-to-HTML conversion process used in the Bookmark Description field. An authenticated user can inject a malicious javascript: URI inside a Markdown link. The vulnerability originates in the filterProtocols method within BookmarkMarkdownFormatter.php.This method attempts to sanitize Markdown links by filtering dangerous protocols (such as javascript:) before rendering. It uses the following regular expression: (#]\((.*?)\)#is). This regex is designed to detect inline Markdown links, but it fails to detect Markdown reference-style links because reference-style links are resolved by the Markdown parser after preprocessing. The filterProtocols method never inspects the actual URL used in these references and as a result, an attacker can supply a javascript: URI inside a reference definition. This issue has been fixed in version 0.16.2.
CVE-2026-48823: Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a stored Cross-Site Scripting (XSS) vulnerability in the tag filtering functionality of Shaarli. An authenticated user can inject arbitrary JavaScript into the tags field when creating a bookmark (Shaare). The malicious payload is stored and later executed when users interact with the "Filter by tag" search feature on the homepage. User-supplied input in the tags field is not properly sanitized or output-escaped before being rendered in the tag filtering interface. When a bookmark is created with a malicious payload inside the tag field, the payload is stored in the database. Later, when a user searches using the "Filter by tag" functionality on the homepage, the application renders matching tags dynamically. If the tag value contains HTML with JavaScript event handlers, it is injected into the DOM. This impacts anyone interacting with the "Filter by tag" search functionality, administrators and privileged users. This issue has been fixed in version 0.16.2.
CVE-2026-50190:

Created: 2026-06-18 Last update: 2026-06-18 20:30

5 security issues in bookworm high

There are 5 open security issues in bookworm.

4 important issues:

CVE-2026-48821: Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a DOM-based Cross-Site Scripting (XSS) vulnerability in the Thumbnail Synchronizer feature. When an administrator runs the thumbnail update process, malicious bookmark titles are returned via an AJAX response and inserted into the DOM using innerHTML without proper sanitization. The issue originates from the interaction between the backend thumbnail update endpoint and the frontend JavaScript responsible for rendering update progress. On the backend, the ThumbnailsController::ajaxUpdate method returns bookmark data formatted using the 'raw' formatter. This includes the unescaped bookmark title in the JSON response. On the client side, the script thumbnails-update.js processes this AJAX response and dynamically updates the progress interface. Administrators using the thumbnail synchronization feature are affected and exploitation could lead to session hijacking, privilege escalation, backdoor injection and full compromise. This issue has been fixed in version 0.16.2.
CVE-2026-48822: Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a stored Cross-Site Scripting (XSS) vulnerability in the Markdown-to-HTML conversion process used in the Bookmark Description field. An authenticated user can inject a malicious javascript: URI inside a Markdown link. The vulnerability originates in the filterProtocols method within BookmarkMarkdownFormatter.php.This method attempts to sanitize Markdown links by filtering dangerous protocols (such as javascript:) before rendering. It uses the following regular expression: (#]\((.*?)\)#is). This regex is designed to detect inline Markdown links, but it fails to detect Markdown reference-style links because reference-style links are resolved by the Markdown parser after preprocessing. The filterProtocols method never inspects the actual URL used in these references and as a result, an attacker can supply a javascript: URI inside a reference definition. This issue has been fixed in version 0.16.2.
CVE-2026-48823: Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a stored Cross-Site Scripting (XSS) vulnerability in the tag filtering functionality of Shaarli. An authenticated user can inject arbitrary JavaScript into the tags field when creating a bookmark (Shaare). The malicious payload is stored and later executed when users interact with the "Filter by tag" search feature on the homepage. User-supplied input in the tags field is not properly sanitized or output-escaped before being rendered in the tag filtering interface. When a bookmark is created with a malicious payload inside the tag field, the payload is stored in the database. Later, when a user searches using the "Filter by tag" functionality on the homepage, the application renders matching tags dynamically. If the tag value contains HTML with JavaScript event handlers, it is injected into the DOM. This impacts anyone interacting with the "Filter by tag" search functionality, administrators and privileged users. This issue has been fixed in version 0.16.2.
CVE-2026-50190:

1 issue left for the package maintainer to handle:

CVE-2023-49469: (needs triaging) Reflected Cross Site Scripting (XSS) vulnerability in Shaarli v0.12.2, allows remote attackers to execute arbitrary code via search tag function.

You can find information about how to handle this issue in the security team's documentation.

Created: 2023-12-28 Last update: 2026-06-18 20:30

The package has not entered testing even though the delay is over normal

The package has not entered testing even though the 5-day delay is over. Check why.

Created: 2026-04-19 Last update: 2026-06-27 16:31

debian/patches: 9 patches to forward upstream low

Among the 23 debian patches available in version 0.16.1+dfsg-1 of the package, we noticed the following issues:

9 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-02-01 09:00

Issues found with some translations low

Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.

Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.

Created: 2021-01-15 Last update: 2021-01-15 02:05

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.2).

Created: 2025-12-23 Last update: 2026-03-31 15:01

testing migrations

excuses:
- Migration status for shaarli (- to 0.16.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ shaarli/amd64 has unsatisfiable dependency
- ∙ ∙ shaarli/arm64 has unsatisfiable dependency
- ∙ ∙ Updating shaarli would introduce bugs in testing: #1128942
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shaarli.html
- ∙ ∙ Autopkgtest skipped on amd64: not installable
- ∙ ∙ Autopkgtest skipped on arm64: not installable
- ∙ ∙ Autopkgtest skipped on i386: not installable (which is allowed)
- ∙ ∙ Autopkgtest skipped on loong64: not installable (which is allowed)
- ∙ ∙ Autopkgtest skipped on ppc64el: not installable (which is allowed)
- ∙ ∙ Autopkgtest skipped on riscv64: not installable (which is allowed)
- ∙ ∙ Autopkgtest skipped on s390x: not installable (which is allowed)
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- ∙ ∙ 146 days old (needed 5 days)
- Not considered

news

[rss feed]

[2026-04-20] shaarli REMOVED from testing (Debian testing watch)
[2026-02-19] Accepted shaarli 0.14.0+dfsg-2+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: James Valleroy)
[2026-02-19] Accepted shaarli 0.12.1+dfsg-8+deb12u2 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: James Valleroy)
[2026-02-09] Accepted shaarli 0.12.1+dfsg-8+deb12u2 (source) into oldstable-security (Debian FTP Masters) (signed by: James Valleroy)
[2026-02-09] Accepted shaarli 0.14.0+dfsg-2+deb13u1 (source) into stable-security (Debian FTP Masters) (signed by: James Valleroy)
[2026-02-03] shaarli 0.16.1+dfsg-1 MIGRATED to testing (Debian testing watch)
[2026-01-31] Accepted shaarli 0.16.1+dfsg-1 (source) into unstable (James Valleroy)
[2025-08-30] Accepted shaarli 0.12.1+dfsg-8+deb12u1 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: James Valleroy)
[2025-08-30] Accepted shaarli 0.14.0+dfsg-2 (source) into proposed-updates (Debian FTP Masters) (signed by: James Valleroy)
[2025-08-25] shaarli 0.15.0+dfsg-1 MIGRATED to testing (Debian testing watch)
[2025-08-22] Accepted shaarli 0.15.0+dfsg-1 (source) into unstable (James Valleroy)
[2025-04-26] shaarli 0.14.0+dfsg-1 MIGRATED to testing (Debian testing watch)
[2025-04-15] Accepted shaarli 0.14.0+dfsg-1 (source) into unstable (James Valleroy)
[2025-03-24] shaarli 0.13.0+dfsg-5 MIGRATED to testing (Debian testing watch)
[2025-03-24] shaarli 0.13.0+dfsg-5 MIGRATED to testing (Debian testing watch)
[2025-03-21] Accepted shaarli 0.13.0+dfsg-5 (source) into unstable (David Prévot)
[2025-01-17] shaarli 0.13.0+dfsg-4 MIGRATED to testing (Debian testing watch)
[2025-01-15] Accepted shaarli 0.13.0+dfsg-4 (source) into unstable (David Prévot)
[2024-10-09] shaarli 0.13.0+dfsg-3 MIGRATED to testing (Debian testing watch)
[2024-08-24] shaarli REMOVED from testing (Debian testing watch)
[2024-03-11] shaarli 0.13.0+dfsg-3 MIGRATED to testing (Debian testing watch)
[2024-03-07] Accepted shaarli 0.13.0+dfsg-3 (source) into unstable (David Prévot)
[2024-02-13] shaarli 0.13.0+dfsg-2 MIGRATED to testing (Debian testing watch)
[2024-02-10] Accepted shaarli 0.13.0+dfsg-2 (source) into unstable (James Valleroy)
[2023-12-21] shaarli 0.13.0+dfsg-1 MIGRATED to testing (Debian testing watch)
[2023-12-15] Accepted shaarli 0.13.0+dfsg-1 (source) into unstable (James Valleroy)
[2023-11-28] shaarli REMOVED from testing (Debian testing watch)
[2023-02-02] Accepted shaarli 0.12.1+dfsg-8~bpo11+1 (source) into bullseye-backports (James Valleroy)
[2023-01-31] shaarli 0.12.1+dfsg-8 MIGRATED to testing (Debian testing watch)
[2023-01-29] Accepted shaarli 0.12.1+dfsg-8 (source) into unstable (James Valleroy)

bugs [bug history graph]

all: 6 7
RC: 1 2
I&N: 5
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian
buildd: logs, debcheck
popcon
browse source code
other distros
security tracker
screenshots
l10n (-, 99)
debian patches
debci