CVE-2026-7320:
Information disclosure due to incorrect boundary conditions in the Audio/Video component. This vulnerability was fixed in Firefox 150.0.1, Firefox ESR 140.10.1, and Firefox ESR 115.35.1.
CVE-2026-7322:
Memory safety bugs present in Firefox ESR 115.35.0, Firefox ESR 140.10.0 and Firefox 150.0.0. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability was fixed in Firefox 150.0.1, Firefox ESR 140.10.1, and Firefox ESR 115.35.1.
CVE-2026-7323:
Memory safety bugs present in Firefox ESR 140.10.0 and Firefox 150.0.0. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability was fixed in Firefox 150.0.1 and Firefox ESR 140.10.1.
CVE-2026-7324:
Memory safety bugs present in Firefox 150.0.0. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability was fixed in Firefox 150.0.1.
Lintian reports
2 errors
and
28 warnings
about this package. You should make the package lintian clean getting rid of them.
Standards version of the package is outdated.
high
The package is severely out of date with respect to the Debian Policy.The package should be updated to follow the last version of Debian Policy
(Standards-Version 4.7.4 instead of
3.9.8.0).
Depends on packages which need a new maintainer
normal
The packages that firefox depends on which need a new maintainer are:
vcswatch reports that
this package seems to have a new changelog entry (version
150.0.1-1, distribution
unstable) and new commits
in its VCS. You should consider whether it's time to make
an upload.
You should get rid of them to provide more metadata about this software.
debian/patches: 18 patches to forward upstream
low
Among the 18 debian patches
available in version 150.0-1 of the package,
we noticed the following issues:
18 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.