dbcve.org
PubnetApplication · Ricardoboss

CVE-2025-65112

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-29
Fix available
A fix is available. Upgrade to 1.1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
PubNet is a self-hosted Dart & Flutter package service. Prior to version 1.1.3, the /api/storage/upload endpoint in PubNet allows unauthenticated users to upload packages as any user by providing arbitrary author-id values. This enables identity spoofing, privilege escalation, and supply chain attacks. This issue has been patched in version 1.1.3.

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 · high confidence

PubNet prior to v1.1.3 has an insecure direct object reference vulnerability in the /api/storage/upload endpoint that allows unauthenticated package uploads with arbitrary author-id values, enabling identity spoofing and supply chain attacks.

MitigationUpgrade to PubNet version 1.1.3 or later. Additionally, implement authentication and validate that the author-id matches the authenticated user making the upload request.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PubnetApplication
Affected:< 1.1.4

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 PubNet version
    Locate the installed PubNet instance and check its version number (commonly found in application metadata, about page, or version file). Compare this to the affected range: versions below 1.1.4.
    Affected if The installed version is below 1.1.4.
  2. Confirm the upload endpoint exists
    Attempt to access or probe the /api/storage/upload endpoint on the PubNet server using a web request tool (curl, browser DevTools, or API client).
    Affected if The /api/storage/upload endpoint is reachable and responds to requests.
  3. Test unauthenticated upload access
    Send a POST request to /api/storage/upload without including any authentication credentials (tokens, API keys, session cookies). Observe whether the request is accepted or rejected.
    Affected if The endpoint accepts and processes upload requests without requiring authentication.
  4. Test arbitrary author-id injection
    In the upload request payload, include a custom author-id value that differs from any legitimate author. Submit the request and check if the uploaded package reflects the arbitrary author-id without validation errors.
    Affected if The uploaded package is stored with the arbitrary author-id value without validation that it matches the authenticated user (or without requiring authentication at all).

A user is affected if PubNet version is below 1.1.4 AND the /api/storage/upload endpoint permits unauthenticated package uploads that accept arbitrary author-id values.

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.

dbcve · scoped
Upgrade available Upgrade to 1.1.4 or later
Fixed in 1.1.4
Interim mitigation

Upgrade to PubNet version 1.1.3 or later. Additionally, implement authentication and validate that the author-id matches the authenticated user making the upload request.

Recommended fix High confidence

Upgrade to PubNet version 1.1.3 or later (recommended: 1.1.4)

  1. 1. Backup your current PubNet installation, including configuration files and stored packages.
  2. 2. Identify your current PubNet version by checking the running service or package manifest.
  3. 3. Consult the official PubNet repository (github.com) for the latest release. Based on the advisory, upgrade to version 1.1.3 or later (version 1.1.4 is noted as the first unaffected version).
  4. 4. Stop the running PubNet service.
  5. 5. Apply the upgrade following the project's documented upgrade procedure (typically involves replacing the binary or updating the package dependencies).
  6. 6. Restart the PubNet service.
  7. 7. Verify the /api/storage/upload endpoint now requires authentication by attempting an unauthenticated request (should be rejected).
  8. 8. Test authenticated package uploads to confirm normal operation is restored.
Caveat Ensure any automated upload scripts or CI/CD pipelines are updated to include proper authentication credentials, as the endpoint no longer accepts unauthenticated requests.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pubnet Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65112 — 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-65112 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