/

CVE-2026-76795

Severity:

HIGH RISK

(7.3)

SSRF (CWE-918) in AeternaLabsHQ PullMD REST API Endpoint

CVE-2026-76795

Deferred

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-918

Impact:

Unauthorized server-side network requests and potential access to internal services

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A server-side request forgery vulnerability in PullMD allows a remote attacker to influence the URL requested by the REST API through the url argument. If the endpoint can reach internal services or restricted network locations, the flaw may expose internal resources or enable further attacks.

Affected context

The vulnerability occurs in the PullMD REST API endpoint at /api when it processes attacker-influenced values supplied through the url argument. Deployments are most exposed when the application server has network access to internal services, cloud metadata endpoints, administrative interfaces, or other destinations that are not directly reachable by external users.

Exploit preconditions

  • Attack surface: The remotely accessible REST API endpoint at /api
  • Required access: Ability to submit requests to the affected endpoint; authentication requirements depend on deployment configuration
  • Trigger point: Server-side handling of the url argument
  • Why exploitation is possible: The application makes outbound requests based on attacker-controlled URL data without sufficiently restricting destinations or validating the request target

Why this happens

The underlying issue is insufficient validation and destination control for a server-side HTTP request. User-supplied URL data is treated as an authorized resource location, allowing the application to act as a network proxy on behalf of an external requester. This behavior maps to CWE-918: Server-Side Request Forgery, in which an attacker can cause a server to send requests to unintended locations.

Potential impact

  • An attacker may retrieve data from internal services that trust requests from the application
  • The application could expose cloud instance metadata or other environment-sensitive information
  • Internal administrative APIs may be accessed or manipulated
  • The flaw could enable reconnaissance and support follow-on attacks against reachable systems
  • Sensitive response content may be disclosed to the attacker

General mitigation guidance

Mitigation generally focuses on reducing trust in user-supplied URLs and enforcing explicit outbound request policies.

Common defensive patterns include:

  • Allowing requests only to an explicit set of approved hosts and schemes
  • Blocking loopback, private, link-local, multicast, and other restricted address ranges
  • Resolving hostnames and validating the resulting addresses before connecting
  • Rechecking destinations after redirects and limiting redirect behavior
  • Restricting outbound network access from the application through egress controls
  • Avoiding unnecessary exposure of response bodies and sensitive error details
  • Running the service with only the network and system privileges it requires

How teams detect issues like this

Organizations can identify SSRF risks through:

  • Static analysis rules for HTTP client calls that consume request parameters
  • Code review checks for URL validation, redirect handling, DNS resolution, and private-address filtering
  • API tests using controlled internal destinations and restricted network ranges
  • Egress monitoring for unexpected connections from the PullMD service
  • Web application firewall or API gateway policies that constrain URL-bearing parameters
  • Automated security review tools that flag user-controlled values reaching outbound network clients

Sources

SourceLink
github.comgithub.com/AeternaLabsHQ/pullmd/
github.comgithub.com/AeternaLabsHQ/pullmd/commit/96448894cc93ccecb0bdcbf263a9d25390a8455e
github.comgithub.com/AeternaLabsHQ/pullmd/issues/41
github.comgithub.com/AeternaLabsHQ/pullmd/pull/42
github.comgithub.com/AeternaLabsHQ/pullmd/releases/tag/v3.3.0
vuldb.comvuldb.com/cve/CVE-2026-76795
vuldb.comvuldb.com/submit/879954
vuldb.comvuldb.com/vuln/393282
vuldb.comvuldb.com/vuln/393282/cti

Frequently asked

questions

Yes. The described attack can be initiated remotely by sending crafted input to the affected REST API, subject to any authentication and access controls enforced by the deployment.

The attacker needs access to the /api endpoint and the ability to influence its url argument. Whether authentication is required depends on the application's configuration.

Treat submitted URLs as untrusted, use an explicit destination allowlist, block restricted network ranges, and apply outbound egress controls as defense in depth.

Review all user-controlled values that reach network clients, test URL and redirect validation, monitor unexpected outbound traffic, and enforce secure API and network policies.

Find out what's already
exploitable in your codebase.