On this page

Atomicorp WAF Research Note: CVE-2026-71365

Awx: webhook status callback ssrf leaks the git pat

CVE Details

Status: Attack Blocked by Atomicorp

Vulnerability Description

A server-side request forgery (SSRF) vulnerability was found in AWX’s webhook status callback mechanism. When processing GitHub pull request webhooks, AWX extracts the status callback URL (pull_request.statuses_url) from the incoming webhook payload without validating the target host against the expected Git provider. This URL is persisted in job extra variables and later used to send authenticated status updates. A user with admin role on a webhook-enabled job template can read the template’s webhook signing key, forge a signed GitHub webhook payload with an arbitrary statuses_url, and cause AWX to POST status updates to an attacker-controlled or internal URL. The status update request includes the configured Git Personal Access Token (PAT) in the Authorization header, resulting in credential leakage to the attacker-specified endpoint.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (337109 , 337110 , 344360 , 390719 , 398021 , 398022 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Versions reported unaffected: Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 8 version 0:4.6.32-1.el8ap.
    • Versions reported unaffected: Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 9 version 0:4.6.32-1.el9ap.
    • Versions reported unaffected: Red Hat Red Hat Ansible Automation Platform 2.6 for RHEL 9 version 0:4.7.16-1.el9ap.
    • Versions reported unaffected: Red Hat Red Hat Ansible Automation Platform 2.6 version 1787244009.
    • Versions reported unaffected: Red Hat Red Hat Ansible Automation Platform 2.7 version 1787220257.
    • CNA guidance source: redhat
    • Vendor workaround: There is no complete mitigation for this vulnerability other than applying the update when available. However, the following measures reduce exposure:

  3. Restrict the admin role on webhook-enabled job templates to trusted personnel who already have legitimate access to the associated Git credentials.

  4. Use Git credentials with the minimum required scope (e.g., read-only access to the specific repository) to limit the impact of credential leakage.

  5. Implement network egress filtering on the Automation Controller nodes to prevent outbound connections to non-allowlisted hosts. Block outbound connections to loopback (127.0.0.0/8), private (RFC1918), and link-local (169.254.0.0/16) address ranges.

  6. Monitor for unusual outbound connections from the Controller node to unexpected destinations.

  7. Rotate Git PAT credentials periodically and after any suspected compromise.

  8. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

  • Source: Atomicorp AI Research Framework
  • Tags: cve, derived, ssrf, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .