Getty Images · Vulnerability Disclosure

Getty Images Vulnerability Disclosure

Vulnerability disclosure

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

ImageMediaPhotosVideosStock PhotographyArtificial IntelligenceSearchContent LicensingDigital Asset ManagementMCP
Program: Hackerone security.txt present

Disclosure Policy

Security Contact

Contact
mailto:security@gettyimages.com

Source

Vulnerability Disclosure

Raw ↑ 
generated: '2026-09-12'
method: searched
probe: true
source: https://www.gettyimages.com/.well-known/security.txt
contact:
- mailto:security@gettyimages.com
evidence:
- source: https://www.gettyimages.com/.well-known/security.txt
  kind: security.txt (live probe)
  status: 200
- source: https://developer.gettyimages.com/release-notes/
  kind: security-relevant change announcements (TLS 1.0/1.1 retirement 2021-01-21, announced 2020-12-03; CloudFront
    cipher policy update 2024-05-08)
  status: 200
policy_url: null
bug_bounty:
  present: false
  platform: null
  note: No HackerOne, Bugcrowd or Intigriti program was found, and the security.txt declares no Policy field.
security_txt:
  url: https://www.gettyimages.com/.well-known/security.txt
  status: 200
  file: well-known/getty-images-security.txt
  fields_present:
  - Contact
  - Expires
  fields_absent:
  - Policy
  - Encryption
  - Acknowledgments
  - Preferred-Languages
  - Canonical
  - Hiring
  expires: '2026-10-01T07:00:00.000Z'
  expiry_note: RFC 9116 requires Expires; Getty sets it 19 days after this probe. A lapsed security.txt reads as
    abandoned, so this one needs refreshing shortly.
  hosts_serving:
  - gettyimages.com
  - www.gettyimages.com
  hosts_not_serving:
  - api.gettyimages.com
  - mcp.gettyimages.com
  - authentication.gettyimages.com
  - scim.gettyimages.com
  - developer.gettyimages.com
api_support_contact: apisupport@gettyimages.com
note: 'Getty runs a minimal but genuine coordinated-disclosure surface: a two-field RFC 9116 security.txt with a
  monitored security@gettyimages.com address, served on the apex and www. There is no published disclosure policy,
  no safe-harbour statement, no bounty and no PGP key, and the document is not served on any of the API, MCP, auth
  or SCIM hosts — a researcher who finds a flaw in api.gettyimages.com has to guess at the corporate domain to find
  the contact.'

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/getty-images-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.

GitHub Google LinkedIn

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