Skip to content

Medium 6.8Patch available

CVE-2025-27591

A privilege escalation vulnerability existed in the Below service prior to v0.9.0 due to the creation of a world-writable directory at /var/log/below. This could have allowed local unprivileged users to escalate to root privileges through symlink attacks that manipulate files such as /etc/shadow.

How scary is it?

updated 21 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • No

    Reachable over the network1

    Needs local access to the machine, such as a shell or a logged-in user (CVSS AV:L).

  • Yes

    Proof-of-concept code is public2

    19 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list3

    Not in the catalog as of our last sync.

Scare-o-meter

Low signal

Limited impact or hard to reach. No rush.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run Meta Platforms, Inc below in an affected version< 0.9.0

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. The attacker already has local access to the machine

    CVSS attack vector: Local (AV:L). Local access required, such as a shell or a logged-in user.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

CVSS
6.8Mediumscored by CISA
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
0.37%chance of exploitation in the next 30 daystop 69% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
11 Mar 2025analysed here 21 Nov 2026

Summary

Triage

Exploitable
At runtime
Attack vector
local
Weakness
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Meta Platforms, Inc below< 0.9.0Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • facebook:below

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 19 GitHub proofs of concept
CISA SSVC
exploitation none, automatable no, technical impact totalAssessed by CISA 21 Mar 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 11 Mar 2025Published
  2. 21 Mar 2025CISA SSVC assessment: exploitation none10 days later
  3. 21 Mar 2025CVE record last updatedsame day later
  4. 12 Jul 2025First proof-of-concept repository on GitHub (unvetted)112 days (about 4 months) later
  5. 21 Nov 2026Analysed by vulneraibility.com497 days (about 1 year) later

CVSS vector

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

MetricValueWhat it means
Attack vectorLocalLocal access required (shell, logged-in user).
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityLowPartial data disclosure.
IntegrityHighComplete modification possible.
AvailabilityNoneThe service stays up.

Common questions

Is CVE-2025-27591 being exploited?

Not confirmed. CVE-2025-27591 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.

How severe is CVE-2025-27591?

CVE-2025-27591 is rated Medium with a CVSS score of 6.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-27591?

Yes. A fix has been recorded for CVE-2025-27591. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-27591 affect?

CVE-2025-27591 affects facebook:below. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

3 references in the CVE record, grouped by the tags the record gives them.

Other links (3)

  • facebook.com /security/advisories/cve-2025-27591
  • github.com /facebookincubator/below/commit/da9382e6e3e332fd2c3195e22f34977f83f0f1f3
  • openwall.com /lists/oss-security/2025/03/12/1

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.