Expedia · Vulnerability Disclosure

Expedia Vulnerability Disclosure

Vulnerability disclosure

Expedia runs a coordinated vulnerability disclosure program on Hackerone. A machine-readable /.well-known/security.txt is served. A dedicated security contact is published.

FlightsHotelsLodgingTravelFortune 500
Program: Hackerone security.txt present

Disclosure Policy

Policy

Security Contact

Contact
RespDisc@expedia.com

Source

Vulnerability Disclosure

expedia-vulnerability-disclosure.yml Raw ↑
generated: '2026-09-07'
method: searched
probe: true
source: https://www.expedia.com/.well-known/security.txt
program:
  type: bug-bounty
  platform: HackerOne
  url: https://hackerone.com/expediagroup_bbp
  name: Expedia Group Bug Bounty
  public: false
  access: >-
    Invite-only. Expedia Group runs the program privately on HackerOne and asks researchers who want an
    invitation to first submit one high-severity issue with a working proof of concept that is in scope.
  rewards: monetary
  evidence:
    url: https://hackerone.com/expediagroup_bbp
    http_status: 200
    fetched: '2026-09-07'
policy:
- https://www.expediagroup.com/about/privacy-data-handling-requirements/
contact:
- RespDisc@expedia.com
hiring:
- https://lifeatexpedia.com/
security_txt:
  url: https://www.expedia.com/.well-known/security.txt
  http_status: 200
  content_type: text/plain
  fields_present: [Contact, Policy, Hiring]
  rfc9116_conformance: non-conformant
  defects:
  - id: dead-policy-link
    severity: high
    detail: >-
      The Policy: URL in Expedia's own security.txt is dead. Probed 2026-09-07,
      https://www.expediagroup.com/about/privacy-data-handling-requirements/ returns HTTP 301 to
      https://www.expediagroup.com/en-us/our-story, which returns HTTP 404 ("There's been a slight
      change in itinerary"). A researcher who follows the disclosure policy link Expedia publishes
      reaches a Page Not Found. This is the provider's to fix.
    evidence:
    - url: https://www.expediagroup.com/about/privacy-data-handling-requirements/
      http_status: 301
      redirects_to: https://www.expediagroup.com/en-us/our-story
    - url: https://www.expediagroup.com/en-us/our-story
      http_status: 404
  - id: no-expires
    severity: medium
    detail: >-
      No Expires: field. RFC 9116 §2.5.5 makes Expires REQUIRED. Without it an automated consumer
      cannot tell whether the file is current, and the document never ages out.
  - id: no-canonical-no-encryption-no-preferred-languages
    severity: low
    detail: Optional but conventional fields Canonical, Encryption and Preferred-Languages are absent.
evidence:
- source: https://www.expedia.com/.well-known/security.txt
  kind: security.txt (live probe)
  http_status: 200
- source: https://hackerone.com/expediagroup_bbp
  kind: bug bounty program page (live probe)
  http_status: 200

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/expedia-vulnerability-disclosure"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.