dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-68049

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Subscriber Broken Access Control in bunny.net <= 2.3.6 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a broken access control vulnerability affecting bunny.net subscriber accounts in versions 2.3.6 and below. The issue allows subscribers to potentially access resources or perform actions outside their intended permissions, likely due to improper validation of user privileges when accessing certain endpoints or data.

MitigationUpgrade to a version higher than 2.3.6. Review access control logic for subscriber-facing endpoints and implement proper authorization checks before granting access to resources or sensitive operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify bunny.net tool or SDK installation
    Check for installed bunny.net CLI, SDK, or related packages on the system. Look for common package managers or project dependencies that reference bunny.net.
    Affected if A bunny.net tool, CLI, or SDK is installed and in use.
  2. Retrieve the installed version
    Use the appropriate command to query the installed version (e.g., --version flag, package manager query, or dependency inspection).
    Affected if The version cannot be determined or is not available.
  3. Compare against affected version range
    Compare the installed version number to the affected range: versions 2.3.6 and below.
    Affected if The installed version is 2.3.6 or lower (e.g., 2.3.6, 2.3.5, 2.3.0, 1.x.x).
  4. Verify subscriber account usage
    Check if the tool or SDK is configured with or being used by bunny.net subscriber accounts for API access, CDN management, or similar operations.
    Affected if Subscriber accounts are actively used for bunny.net services.

The environment is affected if the bunny.net tool or SDK version is 2.3.6 or below and subscriber account features are in use, as the broken access control could allow privilege escalation beyond intended permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a version higher than 2.3.6. Review access control logic for subscriber-facing endpoints and implement proper authorization checks before granting access to resources or sensitive operations.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68049 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data