Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2021-43860: Permissions granted to applications can be hidden from the user at install time

Noroxi assessment

Priority: Monitor (action score 34/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 71.2% of all records.
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: flatpak (AlmaLinux:8) 1.8.7-1.el8; flatpak-devel (AlmaLinux:8) 1.8.7-1.el8; flatpak-libs (AlmaLinux:8) 1.8.7-1.el8.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to flatpak (AlmaLinux:8) 1.8.7-1.el8; flatpak-devel (AlmaLinux:8) 1.8.7-1.el8; flatpak-libs (AlmaLinux:8) 1.8.7-1.el8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Flatpak is a Linux application sandboxing and distribution framework. Prior to versions 1.12.3 and 1.10.6, Flatpak doesn't properly validate that the permissions displayed to the user for an app at install time match the actual permissions granted to the app at runtime, in the case that there's a null byte in the metadata file of an app. Therefore apps can grant themselves permissions without the consent of the user. Flatpak shows permissions to the user during install by reading them from the "xa.metadata" key in the commit metadata. This cannot contain a null terminator, because it is an untrusted GVariant. Flatpak compares these permissions to the *actual* metadata, from the "metadata" file to ensure it wasn't lied to. However, the actual metadata contents are loaded in several places where they are read as simple C-style strings. That means that, if the metadata file includes a null terminator, only the content of the file from *before* the terminator gets compared to xa.metadata. Thus, any permissions that appear in the metadata file after a null terminator are applied at runtime but not shown to the user. So maliciously crafted apps can give themselves hidden permissions. Users who have Flatpaks installed from untrusted sources are at risk in case the Flatpak has a maliciously crafted metadata file, either initially or in an update. This issue is patched in versions 1.12.3 and 1.10.6. As a workaround, users can manually check the permissions of installed apps by checking the metadata file or the xa.metadata key on the commit metadata.

HighCVSS 8.6 · v3.1—No exploit Fix available
Published
Jan 12, 2022
Updated
Jun 17, 2026
EPSS
1.3% · 71th percentile

Report tools

JSON

Action score

34

Monitor

Low priority for now.

CVSS
34 / 40 · 8.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

CNA vs NVD score

NVD
8.6
CNA · GitHub_M
8.2
0.4 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-43860

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
flatpakflatpak
fedoraprojectfedora
redhatenterprise linux
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • debian debian linux11.0
  • debian debian linux9.0
  • fedoraproject fedora35
  • flatpak flatpak1.11.1 and later · up to 1.12.3 inclusive
  • flatpak flatpakbefore 1.10.6
  • redhat enterprise linux8.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • flatpak flatpak

    • >= 1.11.0, < 1.12.3, < 1.10.6affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8flatpakbefore 1.8.7-1.el81.8.7-1.el8
AlmaLinux:8flatpak-develbefore 1.8.7-1.el81.8.7-1.el8
AlmaLinux:8flatpak-libsbefore 1.8.7-1.el81.8.7-1.el8
AlmaLinux:8flatpak-selinuxbefore 1.8.7-1.el81.8.7-1.el8
AlmaLinux:8flatpak-session-helperbefore 1.8.7-1.el81.8.7-1.el8
Debian:11flatpakbefore 1.10.7-0+deb11u11.10.7-0+deb11u1
Debian:12flatpakbefore 1.12.3-11.12.3-1
openSUSE:Leap 15.3flatpakbefore 1.10.7-4.12.11.10.7-4.12.1
openSUSE:Tumbleweedflatpakbefore 1.12.3-1.11.12.3-1.1
Red Hat:enterprise_linux:8::appstreamflatpakbefore 0:1.8.7-1.el80:1.8.7-1.el8
Red Hat:enterprise_linux:8::appstreamflatpak-debuginfobefore 0:1.8.7-1.el80:1.8.7-1.el8
Red Hat:enterprise_linux:8::appstreamflatpak-debugsourcebefore 0:1.8.7-1.el80:1.8.7-1.el8
Red Hat:enterprise_linux:8::appstreamflatpak-libsbefore 0:1.8.7-1.el80:1.8.7-1.el8
Red Hat:enterprise_linux:8::appstreamflatpak-libs-debuginfobefore 0:1.8.7-1.el80:1.8.7-1.el8
Red Hat:enterprise_linux:8::appstreamflatpak-selinuxbefore 0:1.8.7-1.el80:1.8.7-1.el8
Red Hat:enterprise_linux:8::appstreamflatpak-session-helperbefore 0:1.8.7-1.el80:1.8.7-1.el8
Red Hat:enterprise_linux:8::appstreamflatpak-session-helper-debuginfobefore 0:1.8.7-1.el80:1.8.7-1.el8
Red Hat:enterprise_linux:8::appstreamflatpak-tests-debuginfobefore 0:1.8.7-1.el80:1.8.7-1.el8
Red Hat:enterprise_linux:8::crbflatpak-develbefore 0:1.8.7-1.el80:1.8.7-1.el8
Rocky Linux:8flatpakbefore 0:1.8.7-1.el80:1.8.7-1.el8
SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOSflatpakbefore 1.2.3-150100.4.8.11.2.3-150100.4.8.1
SUSE:Linux Enterprise Module for Desktop Applications 15 SP3flatpakbefore 1.10.7-4.12.11.10.7-4.12.1

Other highest-scoring records for the same primary product.

  • CVE-2024-42472Flatpak may allow access to files outside sandbox for certain apps
    40Plan
  • CVE-2026-34078Flatpak has a complete sandbox escape leading to host file access and code execution in the host context
    38Monitor
  • CVE-2019-10063Flatpak before 1.0.8, 1.1.x and 1.2.x before 1.2.4, and 1.3.x before 1.3.1 allows a sandbox bypass.
    37Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2021-21381Mar 11, 2021 · Sandbox escape via special tokens in .desktop file
    32Monitor
  • ← EarlierCVE-2021-41133Oct 8, 2021 · Sandbox bypass via recent VFS-manipulating syscalls
    31Monitor
  • Later →CVE-2022-21682Jan 13, 2022 · flatpak-builder can access files outside the build directory.
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:flatpak1.8.7-1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:flatpak-devel1.8.7-1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:flatpak-libs1.8.7-1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:flatpak-selinux1.8.7-1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:flatpak-session-helper1.8.7-1.el8 · AlmaLinux:8Package registry (OSV)
debian:flatpak1.12.3-1 · Debian:12Package registry (OSV)
opensuse:flatpak1.10.7-4.12.1 · openSUSE:Leap 15.3Package registry (OSV)
red hat:flatpak0:1.8.7-1.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:flatpak-debuginfo0:1.8.7-1.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:flatpak-debugsource0:1.8.7-1.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:flatpak-devel0:1.8.7-1.el8 · Red Hat:enterprise_linux:8::crbPackage registry (OSV)
red hat:flatpak-libs0:1.8.7-1.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:flatpak-libs-debuginfo0:1.8.7-1.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:flatpak-selinux0:1.8.7-1.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:flatpak-session-helper0:1.8.7-1.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:flatpak-session-helper-debuginfo0:1.8.7-1.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:flatpak-tests-debuginfo0:1.8.7-1.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
rocky linux:flatpak0:1.8.7-1.el8 · Rocky Linux:8Package registry (OSV)
suse:flatpak1.10.7-4.12.1 · SUSE:Linux Enterprise Module for Desktop Applications 15 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml
kind: ClusterRolerules:  - apiGroups: ["*"]    resources: ["*"]    verbs: ["*"]

Fixed

yaml
kind: Rolemetadata:  namespace: lodos-systemrules:  - apiGroups: ["apps"]    resources: ["deployments"]    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records